- Does majora/generator-bundle work with Laravel?
- No. It is a Symfony bundle that depends on Symfony's kernel, bundle registration, DI service definitions, and Configuration tree; it will not autoload via Laravel package discovery or register a service provider. In Laravel you would need to port the generator concepts rather than install the package.
- Can I install majora/generator-bundle via Composer in a Laravel app?
- You can require it, but it will not function as intended. It expects Symfony bundle registration in AppKernel or config/bundles.php and Symfony service wiring, neither of which Laravel provides. Without a port, Composer installation just adds an unused dependency.
- What does majora/generator-bundle actually generate?
- It provides Symfony console commands for interactive scaffolding of common components such as entities and CRUD-style structures, with customizable templates and Doctrine-friendly generation. The output is designed to be readable and easy to adapt to your project conventions.
- Is there a Laravel equivalent to majora/generator-bundle?
- Laravel already ships artisan make commands plus publishable stubs for controllers, models, migrations, and more. If you need custom scaffolding, the recommended path is a small first-party package with artisan make commands, config, and stubs/ overrides rather than adopting a Symfony bundle.
- How do I port majora/generator-bundle's scaffolding to Laravel Artisan?
- Start with a short spike to inventory the generator commands and Twig stubs, then separate reusable IP such as field-to-class derivations and naming conventions from Symfony-specific wiring. Build a small internal package exposing Artisan commands and publishable stubs, cribbing the shape from Laravel's own generator commands.
- Is majora/generator-bundle maintained and safe for production?
- No. The repository is archived and has around 2 stars with zero dependents, so there is no maintainer to accept patches, no release cadence, and no security response path. That disqualifies it for production use in most teams' dependency policies.
- Which PHP and Symfony versions does majora/generator-bundle support?
- As a vintage Symfony 2/3-era bundle, it typically targets PHP 5.6 through 7.x and older Symfony versions. Assume it will not run on PHP 8.2+ or current Symfony/Laravel without edits, and verify compatibility before spending spike time.
- What are the alternatives to majora/generator-bundle for Symfony projects?
- Symfony MakerBundle is the maintained, first-party answer for scaffolding entities, CRUD controllers, forms, commands, and tests. It ships with the framework's recommended workflow and is actively supported, unlike this archived bundle.
- Can I use majora/generator-bundle templates with Laravel stubs?
- Not directly. The templates are Twig-based and tied to Symfony bundle conventions, so you cannot drop them into Laravel's stub system. You can study their structure and rewrite the useful parts as Blade or plain PHP stubs for your own Artisan commands.
- Should I adopt majora/generator-bundle or replicate its pattern?
- Replicate the pattern, not the dependency. The value is in its generator opinions, such as naming rules, field-to-class derivations, and folder layout, and those can be harvested into a first-party Laravel package. Adopting an archived Symfony bundle in a Laravel estate adds risk without out-of-the-box fit.