- What is way/generators used for in Laravel?
- way/generators is a Laravel 4-era Artisan extension that scaffolds common files such as models, migrations, controllers, views, seeds, and resources from the command line. It is a developer-time productivity tool, not a runtime dependency. It was useful before modern Laravel shipped native make: commands.
- Does way/generators work with Laravel 5, 6, 7, 8, 9, 10, or 11?
- No. way/generators targets Laravel 4.x and relies on command signatures, namespace layout, PSR-0/classmap-era autoloading, and app/ directory conventions that were replaced in later versions. Its illuminate/support and illuminate/console constraints will not resolve cleanly against a Laravel 5+ composer.json, and forced installs fail at runtime. Modern Laravel projects should use native make: commands instead.
- How do I install way/generators in a Laravel 4 project?
- Run composer require way/generators, then add 'Way\Generators\GeneratorsServiceProvider' to the providers array in app/config/app.php. After that you can run commands such as php artisan generate:model Foo. There is no package configuration or database migration step.
- Is way/generators abandoned or still maintained?
- It is abandoned. The last release was 2014-10-01, and the package has had no fixes for PHP 7/8 incompatibilities or Laravel 4 security backports. Laravel 4 itself has been end-of-life since 2015. Treat it as legacy-only code.
- Which Artisan generator commands does way/generators add?
- It registers commands such as generate:model, generate:migration, generate:resource, generate:scaffold, generate:view, and generate:seed, along with other boilerplate generators. The commands write files into hardcoded app/ paths defined in Laravel 4 configuration. The exact set depends on the package version.
- Can I use way/generators in production?
- No. It is a developer-time scaffolding tool and should never be on a production execution path. In a constrained legacy Laravel 4 app, pin an exact commit, vendor it, and keep it out of production autoloading, for example under require-dev. Do not float it with a caret constraint.
- What are the best alternatives to way/generators for modern Laravel?
- Modern Laravel includes make:model -mfs, make:controller --resource, make:seeder, make:factory, make:request, and make:test out of the box. For multi-file YAML-driven scaffolding, laravel-shift/blueprint is a maintained option, and Laravel Idea provides IDE tooling. These close the capability gap without an unmaintained dependency.
- Why does this way/generators listing show only 28 stars?
- The 28-star figure is far below the roughly 2.5k stars the canonical JeffreyWay/Laravel-4-Generators repository accrued historically. That suggests this listing is a low-confidence fork or mirror rather than the canonical source. Verify provenance and diff against the original before pulling the source into a build.
- Does way/generators support PHP 7 or PHP 8?
- No. It requires the PHP 5.4/5.6 era runtime and has no fixes for PHP 7 or PHP 8 incompatibilities. PHP 5 has been end-of-life since 2018/2019. Running it on newer PHP versions is unsupported and likely to fail.
- Should I fork way/generators for a new Laravel application?
- Generally no. A fork would need its command layer and templates rewritten for modern Laravel, PSR-4 autoloading, and current namespace conventions, and you would own the maintenance and patch SLA. If you want the generator pattern, harvest the opinionated resource-to-model-migration-controller-view-seed design and build internal commands or use Blueprint. Do not adopt the package as-is for greenfield work.