Weave Code
Modelo Bundle Laravel Package
lexik/modelo-bundle
Symfony integration for the Modelo library: registers bundle configuration and services so you can use Modelo models and data-access features in a standard Symfony application. Best suited to projects already using Modelo rather than as a standalone ORM.
Modelo Symfony Bundle
Frequently asked questions about Modelo Bundle
- Is lexik/modelo-bundle compatible with Laravel?
- No. It is a Symfony bundle that registers through config/bundles.php and depends on the Symfony DI container, HttpKernel argument resolvers, and Doctrine ORM. Laravel uses service providers, package discovery, and Eloquent, so there is no supported integration path without a bespoke bridge.
- How do I install lexik/modelo-bundle in a Symfony application?
- Install it with Composer, register the bundle in config/bundles.php, and add the required YAML configuration. Then validate the integration against the project's test suite. It is intended for Symfony projects already using the Modelo library, not as a standalone ORM.
- Does lexik/modelo-bundle support Laravel 10 or Laravel 11?
- No Laravel version is supported because this is not a Laravel package. It has no service provider, no package discovery, and no Eloquent integration. If your application is on Laravel 10 or 11, treat this package as not applicable and use a Laravel-native solution.
- What is lexik/modelo-bundle used for?
- It provides Symfony integration for the Modelo library by registering bundle configuration and services so you can use Modelo models and data-access features in a standard Symfony application. The vendor description suggests a lightweight model layer, while the engineering read describes a runtime dynamic-model system; confirm which product you actually need before adopting it. It is best suited to projects already using Modelo.
- How do I configure lexik/modelo-bundle?
- Configuration is done through Symfony YAML files after registering the bundle in config/bundles.php. There is no Laravel-style config file or service provider. The bundle wires Modelo services into the Symfony container, so verify container compilation and your Modelo-specific settings in a test environment first.
- How do I test lexik/modelo-bundle in my Symfony app?
- Install the bundle in a Symfony test application, register it, and run the project's own test suite plus a minimal Modelo model integration test. Check that the package CI covers the PHP, Symfony, and Doctrine combination you actually run. A dependency constraint bump without a visible CI matrix row is an untested claim, not a verified one.
- Is lexik/modelo-bundle safe for production?
- The v1.0.2 diff is near-zero, a dependency constraint bump with no functional change, but production risk comes from the transitive graph: Symfony 7 pulls PHP 8.2+ and Doctrine ORM majors. The project has a 1.0.x line, one visible maintainer, 1 star, 0 dependents, and no published deprecation or support policy. Treat it as low-maturity plumbing and define an ownership trigger threshold.
- Is lexik/modelo-bundle actively maintained?
- The maturity profile is thin: a 1.0.x line, PRs in single digits, one visible maintainer, 1 star, 0 dependents, and no published support policy. That does not make it unsafe, but it means you should set a fork owner and a trigger threshold such as six months without a release. Also resolve the contradiction between the vendor description and the engineering read before any spike.
- What are Laravel alternatives to lexik/modelo-bundle?
- For request-shaping DTOs and validation, use Laravel-native DTO, validation, and form-request packages rather than a Symfony bundle. If the real requirement is admin-managed dynamic schema, evaluate Laravel-native schema tools against your governance and audit requirements. The underlying need should be captured and routed to a Laravel-native solution, not bridged through Doctrine.
- What PHP, Symfony, and Doctrine versions does lexik/modelo-bundle require?
- Expect a PHP 8.2+ floor under Symfony 7, a Doctrine ORM major dependency, and Lexik shared-bundle conventions. Verify the exact compatibility envelope against the bundle CI rather than assuming it. Teams on Symfony 6.4 LTS can treat it as available but not urgent and fold it into their next planned 7.x move.
Weaver
How can I help you explore Laravel packages today?