- What is medlabmg/youshido-graphql-extended and what does it add?
- It is an extended fork of the Youshido GraphQL library for PHP, packaged under the medlabmg vendor name. The package description says it layers additional types, helpers, and fixes onto the original youshido/graphql code. Its repository name includes Bundle, which strongly suggests it is built as a Symfony bundle. Confirm the exact feature set in the repository before adopting it.
- Does medlabmg/youshido-graphql-extended work with Laravel?
- Not natively. Laravel does not use Symfony bundles, so the package will not be auto-discovered or integrate with Laravel conventions such as config publishing, facades, or service providers. You would need to hand-wire its services into Laravel's container or use a Symfony bridge, which adds architectural debt. For Laravel GraphQL work, prefer a Laravel-native package.
- How do I install medlabmg/youshido-graphql-extended with Composer?
- Installation would normally be via Composer using composer require medlabmg/youshido-graphql-extended, but you must first check its composer.json constraints. Expect PHP 7.x-era and Symfony 3/4 transitive dependencies that may conflict with a modern Laravel skeleton. The repository does not document a supported installation path for Laravel, so test resolution in a throwaway project before committing.
- Which PHP and Laravel versions does this package support?
- The repository excerpt does not state supported PHP or Laravel versions. Given the underlying youshido/graphql library and Symfony bundle packaging, constraints are likely pinned to older PHP 7.x and Symfony 3/4-era components. Laravel version support is effectively unknown and unlikely to be tested. Verify composer.json before assuming compatibility with Laravel 10 or 11.
- Is this a Symfony bundle rather than a Laravel package?
- Yes, the naming and target indicate a Symfony bundle. It extends youshido/graphql, which is distributed as a Symfony bundle, and there is no evidence of a Laravel service provider or package discovery entry. In Laravel this means manual registration and non-standard configuration. Treat it as a Symfony artifact unless the maintainer documents otherwise.
- What does use easily actually include in this extended fork?
- The description only says to use easily and mentions extra types, helpers, and fixes. It does not specify whether the additions cover schema builder helpers, type registries, pagination or Relay helpers, error masking, persisted queries, or dependency-injection conveniences. That functional delta is probably small and should be measured against the code. If it is only boilerplate, reimplementing it on webonyx/graphql-php may be cheaper.
- Is youshido/graphql still maintained, and what does that mean for this fork?
- The upstream youshido/graphql library has been effectively unmaintained for years and has been superseded by webonyx/graphql-php. This fork inherits that abandonment risk, including no PHP 8.x support path and no upstream security patches. There is no visible test or CI signal in the assessment. Check the last commit and release date before relying on it.
- Can I use medlabmg/youshido-graphql-extended safely in production?
- Production use is not recommended on current evidence. The package has zero stars, zero dependents, and no external adoption signal, which means no peer review and no known production deployments outside the publishing organization. It also carries abandoned-upstream risk and potential transitive CVE exposure. If you must use it, isolate it behind an interface and plan an exit to Lighthouse or webonyx/graphql-php.
- What are the best Laravel alternatives for GraphQL if I skip this package?
- For Laravel, Lighthouse is the strongest choice because it is Laravel-native, actively maintained, and wraps webonyx/graphql-php with schema-first SDL, directives, and dataloader batching. Rebing/GraphQL-Laravel is a lower-level option if you want explicit control over type definitions. API Platform is reasonable only if you need REST and GraphQL parity from one resource model. All three avoid the Symfony bundle integration problem.
- What license and testing support does medlabmg/youshido-graphql-extended provide?
- The repository excerpt does not document a license or test suite, and the assessment flags no CI signal. For a Laravel app, there is no standard configuration path: no config publishing, no service provider, and no documented testing approach. Ask the maintainer for the license, commit history, and test coverage, and validate Composer resolution in a spike before treating it as a dependency.