- What is orangehill/generators used for in a Laravel project?
- It is a developer-time scaffolding tool that adds extra Artisan generator commands on top of Laravel's built-in Illuminate\Console\GeneratorCommand infrastructure. Its main draw is make:scaffold plus schema-in-migration ergonomics via make:migration:schema, along with make:pivot and extended make:model and make:controller variants. It ships no middleware, runtime bindings, database or queue surface, so its footprint is limited to a service provider, stub templates and console commands.
- How do I install orangehill/generators?
- Install it with Composer as a dev dependency, for example composer require --dev orangehill/generators, and pin an exact version rather than letting the constraint float. Composer 2 resolution generally works on a Laravel 5.x application with the matching PHP version. On Laravel 5.5 and later the service provider is auto-discovered; on 5.0 through 5.4 you must register it manually.
- Do I need to register the orangehill/generators service provider manually?
- Only on older Laravel releases. On Laravel 5.5 and above the package provider is auto-discovered, so no config changes are required. On Laravel 5.0 through 5.4 you need to add the provider to the providers array in config/app.php before the Artisan commands appear.
- Which Laravel versions does orangehill/generators support?
- It is built for the Laravel 5.x line and constrains illuminate/support to ~5.x, so it effectively pins your application to that legacy branch. Laravel 6 and later reworked generator internals, including stub resolution and model option handling, so the package is not a fit for Laravel 9 or later without a fork. Expect it to either fail Composer resolution or install but break at command execution on modern versions.
- Does orangehill/generators work on PHP 8?
- No. The package targets PHP 5.5.9 through the 7.x line and predates the type and deprecation tightening introduced in PHP 8. On PHP 8.1 or 8.2 you should assume it will not run correctly even if Composer allows the install. Use a pinned legacy PHP version in an isolated environment if you must exercise it.
- Which Artisan commands does orangehill/generators add?
- The package historically registers make:scaffold, make:migration:schema, make:pivot, and extended variants of make:model and make:controller. The most distinctive of these is make:scaffold, which generates a set of related files in one pass. Before adopting it, catalogue which of these commands your team actually invokes, since it is usually only one or two.
- Should orangehill/generators be a production dependency?
- No, treat it strictly as a require-dev entry and exclude it from production builds and container images. It is a developer-time code generation tool with no runtime role in the application. The realistic worst case is a broken Artisan command locally, not a production incident, but keeping it out of production keeps the dependency surface honest.
- How do I customize the stub files used by orangehill/generators?
- The package ships its own stub templates, and the supported route is to override them or maintain a small fork with your team's conventions baked in. Laravel 7 and later offer stub:publish, but on 5.x the equivalent is overriding vendor stubs or writing a thin in-house command. Because the scaffold output is opinionated and frozen in time, plan for reviewers to correct generated boilerplate if you do not fork.
- Is orangehill/generators still maintained?
- Treat it as unmaintained open source regardless of its MIT license. The snapshot shows zero stars and zero dependents, which means no community safety net, no upstream triage and no realistic expectation of a Laravel 10 or 11 port. Pin the exact version, include it in your dependency audit, and be prepared to own a fork if the scaffold command is genuinely valuable to you.
- What are the alternatives to orangehill/generators for Laravel scaffolding?
- Laravel 5.5 and later absorbed much of the practical value into native flags such as make:model -mcr, make:controller --resource --model, make:factory and make:seeder. For teams that want richer generation, maintained options include laravel-shift/blueprint and reliese/laravel, or published native stubs with custom in-house commands. In most cases the native flags close enough of the gap, with make:scaffold as the only real holdout.