Weave Code
Rest Bundle Laravel Package
innmind/rest-bundle
Innmind REST bundle provides a ready-made REST API layer for PHP applications, with routing, serialization, and controller utilities that keep endpoints consistent and configuration minimal.
At a glance
Frequently asked questions about Rest Bundle
- Can I use innmind/rest-bundle in a Laravel application?
- No. innmind/rest-bundle is a Symfony bundle that extends Symfony's bundle class and hooks the Symfony kernel request/response lifecycle, and Laravel has no equivalent bundle registration mechanism for it to plug into. Its HTTP and routing primitives come from the Innmind ecosystem rather than Laravel's request/response objects or router. Treat it as a design reference rather than an installable dependency.
- Does innmind/rest-bundle support Laravel 10 or 11?
- No, not out of the box. The repository is archived and reflects the Symfony 3.4/4.x and PHP 7.x era, so its Composer constraints are unlikely to resolve against Laravel 10 or 11 on PHP 8.1+. Getting any of it running would be a port that translates Laravel's lifecycle into Innmind primitives, not an install. Laravel's own api.php routes, API Resources, and exception handler already cover the same concerns.
- How do I install innmind/rest-bundle with Composer?
- In a Symfony app you would add it with Composer, register the bundle in bundles.php or AppKernel depending on version, and configure its container extension. Because the repository is archived and pins old Symfony and PHP versions, the require may fail on modern PHP, so check the composer.json constraints first. In Laravel there is no bundle registration step, so installation does not apply.
- What does innmind/rest-bundle actually do?
- It provides the Symfony wiring for the Innmind HTTP stack: request handling, resource-oriented verb-to-action routing, JSON request and response handling, PSR-compatible middleware for authentication, validation and error mapping, and container service definitions that keep controllers thin. It deliberately stays out of your domain layer. The heavy lifting lives in the innmind/http and innmind/rest-server packages; the bundle itself is mostly integration glue.
- Is innmind/rest-bundle abandoned or still maintained?
- It is archived, with zero stars and zero dependents. That means no maintainer is patching it, no security advisory feed covers it, and no downstream projects have exercised it in production. You would inherit the patching obligation for the bundle and its pinned transitive dependencies immediately.
- Is innmind/rest-bundle safe to run in production?
- Not recommended. There is no security channel, no maintainer, and no dependents to surface bugs, so any CVE in the bundle or its Innmind transitives is yours to fix. The silent failure mode is a class-not-found or container compile error after an unrelated PHP or Symfony upgrade. For a Laravel team the risk is even more immediate because the Symfony-specific wiring has no place to run.
- What are alternatives to innmind/rest-bundle for building REST APIs in Laravel?
- For Laravel, use the framework's built-in conventions: api.php resource routes, resource controllers, Eloquent API Resources for serialization, FormRequests for validation, Sanctum or Passport for authentication, and Handler.php for standardized error responses. If you want a package, choose actively maintained Laravel API packages rather than a Symfony bundle. innmind/rest-bundle is useful only as a reference model for the build-versus-buy decision.
- Does innmind/rest-bundle handle JSON serialization and content negotiation?
- Yes, content negotiation for JSON and other formats, serialization handlers, and standardized error and status responses are among its advertised capabilities. But those live in the Innmind HTTP components and are wired through Symfony's container and kernel events. In Laravel you would reimplement the same behavior with API Resources, Accept-header middleware, and exception rendering in Handler.php.
- How do I test an API built with innmind/rest-bundle?
- The bundle itself ships no Laravel testing helpers; in Symfony you would use KernelTestCase or WebTestCase against the kernel. If you are borrowing the pattern in Laravel, write normal feature tests with $this->getJson() and $this->postJson() plus assertions on status codes and JSON structure. Test the error mapping and content negotiation paths explicitly, since that is where hand-rolled API layers usually drift.
- Can I copy innmind/rest-bundle's design into a Laravel project?
- Yes, as a pattern rather than code. The transferable ideas are thin controllers, verb-to-action resource routing, immutable value-object HTTP messages, consistent JSON error envelopes, and PSR-style middleware for authentication and validation. Budget a half-day to two-day spike to reimplement those in Laravel idioms; the bundle's own shim adds little once you are writing the bridge.
Weaver
How can I help you explore Laravel packages today?