- How do I install kerigard/laravel-stubs?
- Install it as a Composer dependency in your Laravel project, typically with composer require kerigard/laravel-stubs. After installation, publish the package stubs if you want to customize them. It is designed to fit into your existing Artisan workflow with zero configuration to get started.
- Which Laravel make commands can I customize with this package?
- The package is intended for Laravel's make: code generators, including templates for models, controllers, migrations, factories, seeders, jobs, and similar scaffolds. It lets you override the default stub files instead of editing framework vendor files. The exact set of stubs depends on what Laravel ships and what the package exposes for publishing.
- How do I publish the stub files to my project?
- Use Laravel's standard vendor:publish Artisan workflow to copy the package stubs into your application. Once published, you can edit the copied stub files and commit them with your project. The package is built so you can customize templates without touching files in the vendor directory.
- Does kerigard/laravel-stubs work with Laravel 10 or Laravel 11?
- The package targets Laravel's make: generator workflow, but the supported Laravel versions are defined by its Composer constraints. Check the package metadata for the exact framework version range before installing in a Laravel 10 or Laravel 11 app. In general, packages that override stubs rely on Laravel's publishing and generator behavior.
- Do I need to configure anything after installing the package?
- No, the package is described as requiring zero configuration to get started. You can install it and continue using your normal Artisan make: commands. Configuration only matters when you choose to publish and customize the stub templates.
- Can I customize the model stub to add my own namespace and annotations?
- Yes, the purpose of the package is to let you publish and edit stub templates so generated models follow your conventions. You can adjust boilerplate, namespaces, annotations, and other template content in the published stub files. Subsequent make:model runs will use your customized template instead of the framework default.
- Will custom stubs conflict with Laravel framework updates?
- Custom stubs are kept outside the framework vendor files, which reduces the risk of overwriting changes during Composer updates. You should still review your published stubs after major Laravel upgrades because default templates and generator behavior can change. Version-controlling your stubs makes those reviews easier.
- Can I version-control the published stubs with my application code?
- Yes, publishing stubs into your project lets you commit them alongside your application code. That keeps generated models, controllers, migrations, and other scaffolds consistent across the team. It also gives you a reviewable history when conventions change.
- How is this different from editing Laravel's vendor stub files directly?
- Editing vendor files is fragile because Composer updates can overwrite your changes. This package publishes the stubs into your project so your customizations live with your code and survive dependency updates. It also keeps the overrides explicit and easier for a team to maintain.
- Is kerigard/laravel-stubs suitable for team projects and CI pipelines?
- Yes, it is well suited to teams that want consistent generated code from Artisan make: commands. Committing the customized stubs means every developer and CI job uses the same templates. You can test the generated output in your normal Laravel test suite to confirm conventions are applied.