- What does wn/lumen-generators do?
- It adds Laravel-style Artisan make:* generator commands to Lumen, which ships without Laravel's scaffolding suite. After installing it you can run commands like make:controller, make:model, make:middleware, make:migration, and make:seeder to scaffold common classes. It is a developer convenience layer only; it does not add runtime features or change how your application handles requests.
- How do I install wn/lumen-generators?
- Install it with Composer, ideally as a dev dependency, by running composer require --dev wn/lumen-generators. Then register the package service provider in bootstrap/app.php alongside Lumen's existing providers. Once registered, the make:* commands become available through php artisan. No further configuration is typically required.
- Does wn/lumen-generators work with Lumen 6 or newer?
- No, not reliably. The package was last released in May 2017 and targets the Laravel and Lumen 5.4 to 5.5 era. Lumen 6 and later restructured framework internals and the application skeleton, so the provider may fail to boot or generate files into paths that no longer match current conventions. For Lumen 6 and newer you should plan on replacement rather than adoption.
- Which PHP and Laravel versions does wn/lumen-generators support?
- The package was built for PHP 7.0 and 7.1 idioms on the Lumen 5.4 to 5.5 window. Later PHP 7.x releases may work but can produce warnings. It is not designed for PHP 8 or for modern Lumen and Laravel versions, and its Composer constraints can conflict with newer dependency sets.
- Is wn/lumen-generators safe to use in production?
- It is a development-only tool, so it should never be required at runtime. Install it with require-dev and confirm it is excluded from production builds. The generators only produce boilerplate files during development and have no place on a request path. Treating it as a production dependency adds risk with no benefit.
- Is wn/lumen-generators still maintained?
- No. There have been no commits since 2017, and the project has no active maintainer, security patches, or compatibility updates. That means any bug you hit will be yours to fix. For services expected to outlive the current framework version, it is better to fork it internally or port the few generators you actually use.
- Which make commands does wn/lumen-generators add?
- The package backfills the familiar Laravel generator set, including make:controller, make:model, make:middleware, make:migration, make:seeder, and make:request, along with other common class stubs. Exact command coverage depends on the release you install. Run php artisan list after registration to see the commands available in your installation.
- What are the alternatives to wn/lumen-generators?
- The most reliable alternative is to write a small internal Artisan command set containing only the generators your team actually uses. Another option is to fork or vendor this package under an internal namespace and patch the command signatures for your Lumen skeleton. If you can move to full Laravel, you get native generators without any extra dependency.
- How do I register the service provider for wn/lumen-generators?
- Open bootstrap/app.php and add the package service provider to the $app->register() calls, near the other providers Lumen registers by default. The exact class name is documented in the package README. After saving, run php artisan list to confirm the make:* commands appear. If the provider throws an error, check your Lumen version first.
- How should I test wn/lumen-generators after a framework upgrade?
- Add a smoke test to CI that runs at least one generator command and asserts the expected file is created in the expected path. That catches silent breakage when Lumen or PHP versions change. You should also diff the generated output against your team's current conventions, since old stubs may not reflect modern best practice.