Weave Code
Resource Bundle Laravel Package
programmingarehard/resource-bundle
ProgrammingAreHard ResourceBundle is a Symfony bundle for resource-oriented development. It adds conventions for defining resources and routing RESTful CRUD actions, helping you keep controllers thin and expose consistent APIs with less boilerplate.
Symfony bundle that helps in developing REST APIs.
Frequently asked questions about Resource Bundle
- Is programmingarehard/resource-bundle compatible with Laravel?
- No. It is a Symfony bundle, and Laravel has no bundle concept, so there is no native installation or registration path in a Laravel application. Laravel uses service providers, a different container, and a different HTTP kernel and middleware pipeline. Using it would mean standing up a parallel Symfony kernel or reimplementing its behavior as native Laravel services.
- How do I install programmingarehard/resource-bundle?
- It is designed to be installed with Composer into a Symfony application and registered in the kernel's bundle list. There is no Laravel package discovery or service provider registration. Before attempting an install, inspect its composer.json constraints because resolution against modern PHP and Symfony versions may fail immediately.
- What Symfony and PHP versions does ResourceBundle support?
- The repository shows no clear maintenance signals and likely targets legacy Symfony 2.x-era conventions and PHP 5.x or 7.x features. The available assessment did not confirm a supported version matrix. Expect potential conflicts with PHP 8.x and Symfony 5, 6, or 7, and verify constraints in an isolated environment before relying on it.
- Can I use ResourceBundle to scaffold REST CRUD in Laravel?
- Not directly. Its resource conventions and RESTful routing are built around Symfony controllers and bundle configuration. They do not map onto Laravel routes, resource controllers, or API Resources without a rewrite. You could borrow the design ideas, but the package code itself is not reusable in a Laravel codebase.
- Is programmingarehard/resource-bundle maintained and safe for production?
- The package has very low adoption, zero dependents, and no visible release cadence or issue triage, which suggests it is effectively abandoned. Unmaintained code receives no security patches, and API scaffolding often sits directly in routing, serialization, and content-negotiation paths. Treat it as unverified and high risk for production use.
- What are good alternatives to ResourceBundle for building REST APIs?
- For Symfony, API Platform is the mature and actively maintained choice. For Laravel, use first-party API Resources, resource controllers, route model binding, and validation rather than a Symfony bundle. Fractal or Spatie packages can cover additional serialization and API response needs if the first-party stack is not enough.
- How does ResourceBundle compare to API Platform?
- ResourceBundle is a low-adoption, unmaintained bundle focused on thin CRUD conventions. API Platform is actively maintained and provides resource metadata, serialization, hypermedia, filtering, OpenAPI documentation, and a supported upgrade path. For any new Symfony API, API Platform is the safer baseline.
- Can I fork ResourceBundle and port it to Laravel?
- The MIT license makes forking legally straightforward, but the operational cost is high. Porting means replacing Symfony bundle hooks with Laravel service providers, routes, middleware, and API Resources. Only pursue a fork with a named owner, pinned dependency, and a budget for ongoing PHP and framework upgrade work.
- Does ResourceBundle have a test suite or CI configuration?
- The available assessment does not confirm a green test suite or CI configuration. Without verified tests, treat all behavior as unverified. Check the repository for CI badges, run any existing tests in an isolated container, and inspect composer.json before making a decision.
- What license does ResourceBundle use, and can I use it commercially?
- It is MIT licensed, which permits commercial use, modification, and redistribution with attribution. That permissive license does not offset the maintenance risk of adopting an abandoned dependency. If you fork it, keep the license and attribution intact and assign an owner for future fixes.
Weaver
How can I help you explore Laravel packages today?