- Is m6web/fos-rest-extra-bundle a Laravel package?
- No. It is a Symfony bundle that extends FOSRestBundle with annotation-driven helpers for REST controllers. It has no Laravel service provider, facade, config bridge, or Laravel integration surface. It is not a Laravel package in any practical sense.
- Can I install m6web/fos-rest-extra-bundle in a Laravel application?
- Composer may resolve it, especially with Symfony 6 components present, but installing it adds no callable Laravel functionality. You would still need a Symfony kernel, container, and FOSRestBundle listener pipeline for its annotations and listeners to do anything. For Laravel, use native middleware and API Resources instead.
- What does m6web/fos-rest-extra-bundle actually do?
- It provides annotation-based helpers and listeners on top of FOSRestBundle for common REST concerns such as request and query parameter handling, response formatting, and view integration. It reduces repetitive controller code in Symfony applications already using FOSRestBundle. It does not provide a standalone REST framework.
- Does m6web/fos-rest-extra-bundle support Laravel 10 or Laravel 11?
- It does not target Laravel versions. v4.0.0 only claims Symfony 6 compatibility, which may align with Laravel 10's Symfony 6 components but not necessarily with Laravel 11's Symfony 7 components. Even where Composer resolution succeeds, there is no Laravel integration path. Treat Laravel version support as not applicable.
- How do I install and configure m6web/fos-rest-extra-bundle?
- In Symfony, you install it via Composer, register the bundle in the kernel, and configure it alongside FOSRestBundle. There is no Laravel service provider or configuration bridge, so there is no Laravel installation procedure. The minimal setup claim applies to Symfony bundle registration, not Laravel.
- Is m6web/fos-rest-extra-bundle maintained and safe for production?
- Maintenance is very thin: the package has a single-vendor origin, low adoption, no security policy, and a long gap between releases. v4.0.0 appears to be a terse Symfony 6 compatibility bump rather than evidence of an active maintenance cadence. For production Laravel systems, that support profile is a risk with no offsetting benefit.
- What are the Laravel alternatives to m6web/fos-rest-extra-bundle?
- Use Laravel's first-class primitives: API Resources for response formatting, Form Requests for validation, middleware for content negotiation and header-based versioning, route prefixes and groups, and response macros. These cover the same REST concerns without a Symfony kernel. Most extra helpers map to a few dozen lines of Laravel middleware.
- Can m6web/fos-rest-extra-bundle handle API versioning or content negotiation in Laravel?
- Not in Laravel. Those behaviors in this package are implemented as Symfony and FOSRestBundle listeners and annotations attached to the Symfony request and response event pipeline. Laravel middleware is the correct place to implement header-based versioning, Accept negotiation, and response headers. The package's classes have nothing to attach to in a Laravel app.
- Does v4.0.0 make m6web/fos-rest-extra-bundle compatible with Symfony 7 or Laravel 11?
- The release note only says it makes the bundle compatible with Symfony 6. It does not indicate Symfony 7 support, and an SF6-only constraint can conflict with Laravel 11's Symfony 7 components. Assume a lockfile audit is still required and that fos-rest-bundle interoperability may pin you back.
- Should I use m6web/fos-rest-extra-bundle in a new Laravel project?
- No. It is a Symfony bundle with no Laravel service provider, facade, PSR-15 shim, or config bridge, so it contributes zero callable functionality without a Symfony kernel alongside Laravel. The capability it offers is already covered by Laravel API Resources, response macros, route groups, and middleware. Reject it for a Laravel stack.