Weave Code
Resource Bundle Laravel Package
enhavo/resource-bundle
EnhavoResourceBundle is a PHP bundle for Enhavo applications that packages shared resource functionality into a reusable component, helping developers organize and expose resources consistently across Enhavo-based projects.
At a glance
Frequently asked questions about Resource Bundle
- Is EnhavoResourceBundle a Laravel package?
- No. It is a Symfony bundle for Enhavo, a Symfony CMS, and registers through Symfony's kernel and dependency injection container. It does not ship a Laravel service provider, facade, or Eloquent integration.
- Can I install EnhavoResourceBundle in a Laravel application?
- Composer may resolve it, but it is category-wrong for Laravel. It expects Symfony bundle semantics and likely Doctrine-based persistence, so bridging it into Laravel's container is real engineering rather than configuration. The practical options are running Enhavo separately or reimplementing the needed behavior natively in Laravel.
- What Laravel versions does EnhavoResourceBundle support?
- None are stated. The README is only a heading and there is no Laravel support matrix or usage documentation. Treat Laravel compatibility as unknown and verify its Symfony and PHP constraints in composer.json before any commitment.
- How do I install EnhavoResourceBundle?
- The normal Composer command is composer require enhavo/resource-bundle, but that only makes sense inside a compatible Symfony or Enhavo application. In Laravel, first run composer why-not enhavo/resource-bundle on a throwaway branch. Check its composer.json for symfony/*, doctrine/*, and php constraints, plus PSR-4 autoloading and license.
- Why does composer require enhavo/resource-bundle fail in my Laravel project?
- Laravel pins Symfony components such as http-kernel and console to versions tied to the Laravel release. An Enhavo bundle will usually constrain those same packages to a different range, causing dependency resolution conflicts before any code runs. Use composer why-not against your current composer.json to identify the exact conflict.
- What is EnhavoResourceBundle used for?
- It packages shared resource functionality for Enhavo applications. The public description says it helps developers organize and expose resources consistently across Enhavo-based projects. With no usage docs, you must read the source to scope whether it covers routing, admin CRUD, metadata, or something else.
- Does EnhavoResourceBundle integrate with Laravel API Resources, policies, or Eloquent?
- No. It is a Symfony bundle and has no service provider, facade, or Eloquent integration. Its resource abstraction may overlap conceptually with Laravel API Resources and policies, but it is not interchangeable with them. Do not assume Laravel-native behavior.
- How do I test EnhavoResourceBundle in a Laravel app?
- A one-day spike is the right scope: fork or require it on a throwaway branch, run composer why-not, and inspect the bundle's DependencyInjection extension and service definitions. Confirm whether it requires Enhavo core bundles that it does not declare. If the container shim becomes substantial, stop and choose a different integration pattern.
- Is EnhavoResourceBundle production-ready and maintained?
- There is no evidence of community adoption: zero stars, zero dependents, and a README that is only a heading. That means no documented security patch path and no upgrade guidance. Treat technical risk as high until upstream ownership, license, and release history are verified.
- What are Laravel-friendly alternatives to EnhavoResourceBundle?
- For Laravel, use Laravel API Resources, policies, form requests, and Eloquent for the same resource organization concerns. If you need Enhavo itself, run it as a standalone Symfony application and consume it over HTTP from Laravel. Installing the bundle inside Laravel and shimming the container costs more and buys less.
Weaver
How can I help you explore Laravel packages today?