Weave Code
Rest Bundle Laravel Package
silpo-tech/rest-bundle
REST Bundle from Silpo Tech provides a foundation for building RESTful APIs in PHP applications, with conventions and utilities to streamline request handling, serialization, and responses. It aims to reduce boilerplate for common API tasks.
At a glance
Frequently asked questions about Rest Bundle
- Is silpo-tech/rest-bundle a Laravel package?
- No. It is a Symfony bundle that ships a Bundle class, a DependencyInjection Extension with a config tree, compiler passes, and tagged services, none of which Laravel's service container consumes. Composer will install it, but nothing gets registered in a Laravel application. Treat it as a reference implementation to study or port rather than a dependency to install.
- Can I install silpo-tech/rest-bundle with Composer in a Laravel app?
- You can run composer require, but it registers nothing in Laravel, and Symfony 6.x and 7.x component pins can collide with the versions Illuminate constrains, so resolution failure is a realistic outcome. Even a successful install leaves you with a dead dependency. If you want the code, fork or vendor it under an internal namespace instead of depending on the upstream repository as a Composer source.
- What does silpo-tech/rest-bundle actually do?
- Its stated purpose is to provide a foundation for building RESTful APIs in PHP, with conventions and utilities that streamline request handling, serialization, and responses to cut boilerplate. What that means in practice depends on the source: response factories, an error envelope, and serializer normalizers port quickly, while kernel.view or kernel.exception listeners and request-to-DTO mapping become a rewrite of the request lifecycle. The evaluation flags the scope as unverified because the README excerpt was empty, so read the code before estimating.
- Which Symfony extension points does this bundle register?
- Per the technical evaluation it ships a Bundle class, a DependencyInjection Extension with a config tree, compiler passes, and tagged services. Whether it also registers event subscribers, routing loaders, or kernel listeners is not confirmed and should be checked first, because that determines porting cost. Anything hooking kernel.view or kernel.exception becomes middleware and exception-handler work in Laravel.
- Which Symfony and PHP versions does it support?
- Symfony component pins in the 6.x and 7.x lines are noted, and the evaluation warns the supported Symfony and PHP matrix may be implied by CI rather than declared in composer.json. There is no Laravel version support to speak of because it is not a Laravel package. Verify the constraints and whether CI runs a version matrix or a single pinned version before planning anything.
- How do I port this bundle to Laravel?
- Fork and re-home the code under an internal namespace rather than depending on upstream. Convert the Bundle and Extension into a ServiceProvider using mergeConfigFrom and publishes, move the configuration tree into config/rest.php with validation in register and boot, and replace listeners with middleware or the exception handler. Map any request-to-DTO logic onto FormRequest and response shaping onto API Resources or the Responsable contract.
- Does adopting it lock me into Silpo's API conventions?
- Likely yes. Bundles of this type typically hard-code an error envelope, status-code policy, serialization groups, and a pagination shape, so adopting them means inheriting another company's API contract. If you run Symfony alongside Laravel, mirroring those contracts keeps both surfaces consistent, but a Laravel-only team should reimplement only the useful piece natively.
- Is silpo-tech/rest-bundle actively maintained and safe for production?
- Risky on both counts. It has zero stars, zero dependents, and no public consumers outside Silpo, so there is no external evidence of correctness and no third-party bug reports for edge cases. A 2025-10-03 release looks current, but a single tag can be an automated dependency bump, and with no dependents breakage goes undetected by anyone but the owner. Fork it, vendor it, and add your own test coverage.
- What license is silpo-tech/rest-bundle under, and can I fork it?
- MIT, which is permissive and unproblematic for forking or vendoring. The recommendation is to fork and re-home the code under an internal namespace instead of depending on the upstream repository as a Composer source. Keep the license notice when you do.
- What are the Laravel-native alternatives to this bundle?
- Laravel's HTTP layer already covers content negotiation, validation-to-422, resource transformation, and exception rendering. FormRequest handles validation and authorization, API Resources and Responsable shape responses, and the exception Handler renders errors consistently. For a Laravel-only team the bundle's marginal value is small and the coupling cost is high.
Weaver
How can I help you explore Laravel packages today?