- What is milwad/laravel-crod and what does it actually generate?
- Laravel Crod is a dev-time CRUD scaffolding package for Laravel that produces a full vertical slice from a single Artisan command. Depending on your stub configuration it emits a controller, model, migration, form request, API resource, routes and views, plus optional service or action classes. It is not a runtime library: the output is plain PHP added to your repository, and the package itself never executes in production.
- Which Laravel and PHP versions does Laravel Crod support?
- Laravel Crod targets modern Laravel applications, with the maintainers documenting support for Laravel 9 through 12 on PHP 8.1 and above. Because Laravel majors ship quickly, verify the exact Laravel and PHP matrix in the package's README and composer.json rather than inferring it from the release date. Also check whether that matrix is covered by the package's own CI before you pin a version.
- How do I install laravel-crod in a Laravel project?
- Install it with Composer as a dev dependency, for example composer require --dev milwad/laravel-crod, so it stays out of your production autoload graph. Then publish the config and stubs into your repository so they are version-controlled and reviewable. After that you run the generator command and commit the generated files like any other code.
- Is laravel-crod a runtime dependency I need in production?
- No. Laravel Crod is a scaffolding tool that only runs on your machine or in CI, and it registers no middleware, request lifecycle hooks or database behaviour. Everything it produces is ordinary PHP source that you own and can edit freely. Installing it with require-dev keeps it out of production deployments entirely.
- Can I customize the stubs so generated code matches my team's conventions?
- Yes, the package is built around publishable, overridable stubs, so you can rewrite them to express your own layering, namespace and directory conventions. This is the key step for team adoption: rewrite stubs for authorization, transactions, pagination, DTO or enum usage, and test skeletons before rolling it out. Confirm that every stub, including namespace and placement, is publishable in your version, because partial override support erodes the time savings.
- Does Laravel Crod generate tests, factories, policies and relationship-aware migrations?
- The core output is the controller, model, migration, form request, resource and routes, with supporting service or action classes depending on your stubs. Tests, factories, policies and rich relationship definitions are generally not included by default, so add them to your published stubs if your standards require them. Treat the generator as a starting point and enforce a post-generation quality gate such as Pint plus PHPStan or Larastan.
- Does Laravel Crod support API and web scaffolding, and can I generate only one?
- Laravel Crod is designed to scaffold both web and API style CRUD, with the exact split controlled by the command options and the stubs you publish. If you only need one flavour, disable or remove the other in your stubs so unused routes and views are never emitted. Check the command signature in the README for the flags your installed version exposes.
- Will laravel-crod overwrite files I already have in my project?
- A well-behaved generator should refuse to clobber existing files, and you should verify this behaviour before running it on a dirty working tree. Run the command on a clean branch first and confirm the overwrite or idempotency guard actually triggers. This is the one realistic data-loss path with scaffolding tools, so test it once deliberately.
- Does Laravel Crod conflict with make:model, make:controller or other CRUD generators?
- No, it coexists with Laravel's built-in make:* commands and with tools like Pint, PHPStan, Larastan and Rector. It is best described as an opinionated superset of make:model and make:controller that emits an entire slice at once rather than a single class. You can keep using the native generators for one-off classes and reach for Crod when you need a full resource.
- Should I use laravel-crod on an existing Laravel codebase or only for new features?
- Use it for new verticals only. Retrofitting existing code would churn files for no business value, and generated output will not match code that evolved under different conventions. The package is maintained by a single author with a small install base, which is acceptable here because the artifact is source code you own after generation; still, pin an exact version in composer.lock and review the maintainer's recent release and issue cadence before adopting.