Weave Code
Generator Bundle Laravel Package
kunstmaan/generator-bundle
Kunstmaan GeneratorBundle offers Symfony command-line generators for quickly scaffolding bundles, entities, admin pages, and CRUD functionality, helping developers build Kunstmaan CMS projects faster with consistent boilerplate and sensible defaults.
Kunstmaan GeneratorBundle is a Symfony bundle that accelerates development by generating boilerplate code for Kunstmaan-based applications. It provides commands and templates for scaffolding CRUD, admin lists, pages, and related bundle components, helping teams keep structure consistent while reducing repetitive setup.
- Generates CRUD and admin list code from existing entities
- Scaffolds page and bundle components
- Uses customizable templates and generator commands
- Integrates with Kunstmaan Bundles workflows
- Reduces boilerplate and enforces conventions
Frequently asked questions about Generator Bundle
- Is kunstmaan/generator-bundle a Laravel package?
- No. It is a legacy Symfony bundle from the Symfony 2 era, not a Laravel package. It does not provide Laravel service providers, package auto-discovery, or Artisan commands. Treat it as a conceptual reference rather than a Laravel dependency.
- Can I install kunstmaan/generator-bundle in a Laravel application with Composer?
- Direct Composer installation is not recommended and may fail because of legacy Symfony dependency constraints. Even if it installs, it would add unnecessary Symfony dependencies to a Laravel application. If you need to inspect it, run a time-boxed spike outside production rather than adding it to your app.
- What is kunstmaan/generator-bundle used for?
- It scaffolds Symfony bundles, entities, admin pages, and CRUD structures from simple commands. In Laravel terms, that maps to Artisan make commands, custom stubs, and admin resource generators. It was built for Kunstmaan's Symfony CMS, not for Laravel applications.
- Does kunstmaan/generator-bundle support Laravel 10 or Laravel 11?
- No. The package predates modern Laravel and targets legacy Symfony and PHP APIs. It has no Laravel version constraints or Laravel integration points. Do not expect it to work with Laravel 10, Laravel 11, or current PHP versions without significant changes.
- Is kunstmaan/generator-bundle maintained?
- No, it is effectively unmaintained. The last release was in 2014, the star count is low, and it has no dependents. Your team would own any fixes, compatibility work, and security review if you adopt or fork it.
- What are the alternatives to kunstmaan/generator-bundle for Laravel developers?
- Use Laravel's built-in Artisan make commands and custom stubs for scaffolding. For admin CRUD, consider Filament or Nova-style resource generators. Laravel starter kits and internal package skeletons cover the starter-site and bundle-skeleton use cases.
- How do I migrate Kunstmaan generator ideas to Laravel Artisan commands?
- Inventory the generator behaviors you actually need, such as bundle skeletons, admin lists, and CRUD. Map each behavior to a Laravel-native Artisan command or stub set. Prototype the highest-value generator first and add golden-file tests for generated output. Reuse templates only after checking the MIT license and updating legacy assumptions.
- What technical risks come with using kunstmaan/generator-bundle?
- Expect Composer dependency conflicts, unsupported PHP and Symfony APIs, and command incompatibility. Generated code may not follow Laravel conventions and can become stale or insecure. Regeneration overwrite behavior is another risk to test before relying on it.
- Can I reuse the templates or code from kunstmaan/generator-bundle?
- The package is MIT licensed, so reuse is generally permitted with attribution and license compliance. However, the templates target legacy Symfony conventions and should be reviewed before reuse. A clean-room Laravel implementation is often safer than copying command logic directly.
- Should we fork kunstmaan/generator-bundle for internal use?
- Only if a short spike proves clear developer-productivity value and you can assign ownership. A small internal fork or clean-room Laravel package is preferable to adding the legacy bundle to production applications. Otherwise, extract the useful patterns, build Laravel-native generators, and stop.
Weaver
How can I help you explore Laravel packages today?