Weave Code
Rest Bundle Laravel Package
ibrows/rest-bundle
A Symfony bundle for building RESTful APIs with annotated controllers, automatic serialization, and configurable response formats. It helps expose clean JSON/XML endpoints and integrate REST resources into Symfony applications with less boilerplate.
Provide some additional features to FOSRest
Frequently asked questions about Rest Bundle
- Is ibrows/rest-bundle a Laravel package?
- No. ibrows/rest-bundle is a Symfony bundle that extends friendsofsymfony/rest-bundle (FOSRestBundle), and it relies on Symfony's HttpKernel, EventDispatcher, and DependencyInjection model. Laravel has no bundle registration mechanism or compatible service container compiler passes, so there is no straightforward way to use it in a Laravel application. For Laravel REST APIs, use native routing, API Resources, FormRequests, and Sanctum instead.
- How do I install ibrows/rest-bundle?
- Install it with Composer using composer require ibrows/rest-bundle, then enable the bundle in your Symfony application's bundle configuration. You will also need a compatible FOSRestBundle and Symfony version in the dependency tree. There is no Laravel package discovery or config publishing step because this is not a Laravel package. Check Composer constraints before installing, since the dependency chain may be tied to older Symfony releases.
- Does ibrows/rest-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony and FOSRestBundle, not Laravel, so Laravel 10 and Laravel 11 are not supported targets. Laravel's request lifecycle, middleware pipeline, validation, and serialization layers are self-contained and do not provide the Symfony bundle hooks this package expects. Use Laravel's built-in API routing, Eloquent API Resources, FormRequest validation, and response()->json() for equivalent behavior.
- What does ibrows/rest-bundle add to FOSRestBundle?
- The package is described as providing additional features on top of FOSRestBundle for annotated REST controllers, automatic serialization, and configurable response formats. It is a thin add-on rather than a standalone framework, so its behavior depends heavily on the underlying FOSRestBundle and Symfony serializer versions. Because the repository has no visible community traction, verify the exact feature set in the source before relying on any specific capability.
- Can I use ibrows/rest-bundle with Symfony 6 or Symfony 7?
- That is uncertain and should be treated as high risk. The bundle is likely tied to Symfony 4 or 5-era extension points, and Symfony 6 and 7 removed or deprecated several APIs that older bundles relied on. You would need to verify the Composer constraints and run a real integration test before assuming compatibility. Given the unmaintained dependency tree, expect conflicts with modern symfony/serializer and related packages.
- What are the Laravel alternatives to ibrows/rest-bundle?
- In Laravel, use Route::apiResource() for RESTful routes, API Resource classes for response transformation, FormRequest classes for validation, and Sanctum or Passport for authentication. Content negotiation and JSON responses are handled natively through response()->json(), Accept headers, and middleware. If you need a fuller API specification workflow, evaluate API Platform only in a Symfony context; for Laravel, native features plus packages like Spatie Query Builder or Fractal are more appropriate.
- Is ibrows/rest-bundle maintained and safe for production?
- The available assessment shows zero stars, zero dependents, and no evidence of a test suite or CI, which is a poor production signal. The package also inherits the support and deprecation status of FOSRestBundle, which has been superseded by native Symfony routing and serialization features. Adopting it would likely make your team the de facto maintainer of an unmaintained Symfony-era shim. Treat transitive security issues in the FOSRestBundle and Symfony serializer chain as your responsibility if you proceed.
- How do I test a REST API built with ibrows/rest-bundle?
- You would test it as a Symfony bundle, using Symfony's test client and functional tests against routes configured through FOSRestBundle and your annotated controllers. There is no Laravel-style HTTP test helper or package-specific test suite documented in the provided context. Build your own coverage for content negotiation, serialization output, error handling, and format switching. If the package has no CI, pin versions and add regression tests before any production use.
- How do I migrate from FOSRestBundle or ibrows/rest-bundle to Laravel?
- Treat it as a rewrite of the API surface, not a library swap. Map FOSRestBundle annotations and attributes to native Laravel Route definitions, map param fetchers to typed controller arguments and FormRequest validation, map view listeners to API Resource classes, and map exception handling to Laravel's exception handler. Do not try to port the Symfony bundle or its dependency chain into Laravel. Budget the work as a framework migration with API contract tests.
- Does ibrows/rest-bundle work with PHP 8 and modern Composer?
- It may not. The package likely pins older Symfony and FOSRestBundle constraints, and those constraints can block PHP 8 upgrades or conflict with modern Composer resolution. Check the composer.json requirements for PHP and Symfony versions before adding it to any project. In a Laravel stack, PHP version drift from an unrelated Symfony dependency is a strong reason to avoid the package entirely.
Weaver
How can I help you explore Laravel packages today?