- What is xammie/make-commands used for?
- It adds extra Artisan generator commands to Laravel for scaffolding common PHP classes such as actions, services, and DTOs. It helps teams keep new files consistent by using customizable stubs. It is best treated as a development productivity package rather than production runtime code.
- How do I install xammie/make-commands in Laravel?
- Install it with Composer, preferably as a dev dependency, for example composer require --dev xammie/make-commands. Then confirm the package service provider is discovered or registered according to its README. Run php artisan list to verify the additional make commands are available.
- Does xammie/make-commands support Laravel 10 and which PHP versions?
- Version 0.5.0 is an additive compatibility release that adds Laravel 10 support, and Laravel 10 itself requires PHP 8.1 or newer. The provided context does not list exact package PHP constraints, so check composer.json before rollout. Validate in CI with your target Laravel 10 and PHP matrix.
- Does v0.5.0 still support Laravel 9?
- The v0.5.0 release is described as compatibility-expanding and additive, but the provided context does not explicitly confirm retained Laravel 9 support. Check the package composer.json constraints and release notes before relying on it for a Laravel 9 project. If you need both versions, validate the upgrade in CI against each supported Laravel and PHP combination.
- Should xammie/make-commands be a require-dev dependency?
- Yes, it is developer tooling for generating classes, not runtime application code, so require-dev is the appropriate default. Keeping it out of production dependencies reduces operational risk and avoids shipping scaffolding commands where they are not needed. Pin it with ^0.5.0 or an exact version and rely on composer.lock for reproducible developer environments.
- How do I customize the stubs used by make-commands?
- The package supports customizable stubs so generated actions, services, DTOs, and similar classes can match your project conventions. Follow the package README for publishing or editing stubs and for any configuration options. After changes, generate a sample class in a branch and review the output before rolling it out to the team.
- Are there Artisan command name collisions with Laravel built-in make commands?
- Possible collisions should be checked because the package adds extra make-style commands alongside Laravel built-in generators. Run php artisan list before and after installation and look for duplicate or overridden command names. If a collision appears, review command signatures and namespaces, and test the affected commands in CI.
- How should I test xammie/make-commands in CI?
- Add the package to a development or CI job using your target Laravel and PHP versions. Run composer install, php artisan list, and smoke-test each generator command you plan to use. Generate sample classes and assert that the expected files and namespaces are produced, then remove or ignore generated fixtures as appropriate.
- What alternatives exist to xammie/make-commands for Laravel scaffolding?
- Laravel built-in Artisan make commands cover standard classes, and custom stubs can be added for project-specific conventions without an extra package. Some teams use other generator packages or internal scaffolding scripts. Compare command coverage, Laravel version support, maintenance activity, and whether the package fits a require-dev workflow.
- What are the risks of using a pre-1.0 package like xammie/make-commands?
- It is pre-1.0 and likely community-supported, so minor releases can still introduce breaking changes and there may be no SLA. The TPM assessment also flags single-maintainer risk, so identify whether your team can fork or patch it if needed. Pin the version, monitor upstream releases, and keep usage limited to development environments.