- Is mi/rest-extra-bundle a Laravel package?
- No. mi/rest-extra-bundle is a Symfony HttpKernel bundle that ships a Bundle subclass, a DI extension, and a convention-based routing loader. Laravel has no bundle registration, no FOSRestBundle, and no SensioFrameworkExtraBundle, so this package cannot be leveraged in a Laravel codebase. If your target stack is Laravel, stack fit is effectively zero.
- Can I use mi/rest-extra-bundle in a Laravel application?
- No. Composer may resolve it, but Laravel cannot register or boot a Symfony bundle and does not provide the FOSRestBundle or SensioFrameworkExtraBundle layers this package depends on. There is no service provider, no Laravel route loader integration, and no meaningful port path. Use Laravel's native routing and request handling instead.
- What does mi/rest-extra-bundle actually do?
- It adds a thin opinion layer on top of FOSRestBundle and SensioFrameworkExtraBundle, mainly a convention-based routing loader and REST helpers that let you avoid annotation-based route declarations. It does not own persistence, serialization, or HTTP negotiation. The value is roughly 50 to 150 lines of custom route loader, so judge adoption against that baseline.
- Which Symfony versions does mi/rest-extra-bundle support?
- The last release was 2021-07-02, which predates mature PHP 8.1, 8.2, and 8.3 support and Symfony 6. It is only realistically viable on Symfony 5.4 or earlier where annotation configuration is still permitted. Expect Composer constraint conflicts and deprecation noise on newer stacks.
- Does mi/rest-extra-bundle work with Symfony 6 or Symfony 7?
- It is not viable on Symfony 6.3+ or Symfony 7. SensioFrameworkExtraBundle annotation support was deprecated in Symfony 6.2, and annotation-based configuration was removed in Symfony 7, while FOSRestBundle is in maintenance mode. Attribute routing and routes.yaml already deliver the stated benefit without adding a 2021 bundle.
- What are Laravel-native alternatives to mi/rest-extra-bundle?
- Laravel already provides Route::apiResource, implicit controller binding, Form Requests, and API Resources for building consistent JSON APIs. These cover the same REST conveniences without a third-party abstraction layer. Do not attempt to port this Symfony bundle into Laravel.
- Is mi/rest-extra-bundle still maintained?
- There are zero validation signals: 0 stars, 0 dependents, single-org provenance, and a last release dated 2021-07-02. Assume a bus factor of one and possible repository archival. The automated opportunity score should be heavily discounted because no adoption evidence corroborates it.
- What dependencies does mi/rest-extra-bundle require?
- It requires a Symfony HttpKernel application plus FOSRestBundle and SensioFrameworkExtraBundle to be useful. That means adoption amplifies dependency surface on two packages that are themselves declining or in maintenance mode. It does not provision databases, external services, or persistence, so isolation and removal are cheap if you keep route config behind your own layer.
- How should I test mi/rest-extra-bundle before adopting it?
- Pilot it on one low-traffic controller in a legacy Symfony 5.4 or earlier service and diff the generated routes against your existing annotations. Confirm the loader handles nested prefixes, requirements, HTTP method matrices, and versioning before rolling it out. A routing loader failure appears as a 404 or route collision in production, not a warning.
- Should I fork mi/rest-extra-bundle for a production Symfony app?
- Only if you have a Symfony 5.4 or earlier service with a concrete annotation burden and a near-term modernization plan. Vendor it into an internal namespace, pin constraints, add a PHP 8.x CI matrix and changelog, and assign an internal owner from day one. Treat upstream as archived and do not adopt it on Symfony 6.3+ or Symfony 7.