- How do I install and run basic scaffolding commands like generating a controller or CRUD structure?
- Install via Composer with `composer require adereksisusanto/laravel-artisan`, then run commands like `php artisan artisan:make:controller` or `php artisan artisan:make:crud`. The package integrates directly with Laravel’s Artisan CLI, so no additional configuration is needed for basic use. Ensure your project uses Laravel 10+ and PHP 8.2+ for compatibility.
- Can this package generate API resources, migrations, or test stubs alongside controllers?
- Yes, the package supports generating migrations, factories, and test stubs (e.g., Pest or PHPUnit) alongside controllers. Use commands like `php artisan artisan:make:api-resource` or `php artisan artisan:make:model --with-migration --with-factory --with-tests` to scaffold full resource structures. Customize the output by publishing and overriding the default Blade templates.
- Does this work with Laravel 11 or newer versions? Are there breaking changes to watch for?
- The package claims PHP 8.2+ and Laravel 10+ compatibility, but since it lacks active maintenance, there’s a risk of breaking changes in newer Laravel versions. Test thoroughly in a staging environment before adopting it in production. If using Laravel 11+, monitor for Artisan command structure updates that might affect the package’s functionality.
- How can I customize the generated code (e.g., add team-specific naming conventions or business logic)?
- Customize templates by publishing the package’s assets with `php artisan vendor:publish --tag=artisan-templates`. Override the Blade templates in `resources/views/vendor/artisan/` to modify the generated code structure, naming conventions, or add custom logic. You can also extend the package by creating custom commands using Laravel’s `Artisan::extend()` method.
- Is this package suitable for large-scale or multi-module Laravel applications?
- The package is designed for modular scaffolding, making it viable for multi-module projects, but its limited adoption and lack of documentation suggest it may not handle complex dependencies or multi-tenant architectures out of the box. Test it in a sandbox environment first to ensure it meets your team’s specific scaffolding needs, especially for shared or reusable modules.
- What alternatives exist if this package doesn’t meet my needs (e.g., for API-first or microservices)?
- For API-first projects, consider Laravel’s built-in `make:api-resource` or packages like `spatie/laravel-api-resource`. For microservices, custom Artisan commands or tools like Laravel Forge/Sail for infrastructure scaffolding may be better. If you need CMS-specific boilerplates, Statamic or October CMS offer more tailored solutions. Evaluate whether your use case aligns with this package’s monolithic scaffolding approach.
- How do I integrate this into CI/CD pipelines (e.g., GitHub Actions) for automated scaffolding?
- Since the package lacks built-in CI/CD hooks, you’ll need to manually add commands like `php artisan artisan:make:crud` to your pipeline scripts. For GitHub Actions, include it in a workflow step during the `setup` or `build` phase. Test the pipeline in a non-production branch first to avoid breaking changes. Consider isolating scaffolding to development environments until stability is confirmed.
- Are there any known issues or edge cases where this package might fail in production?
- The package has no visible test suite or active maintenance, so edge cases—like conflicts with custom Artisan commands or Laravel core updates—could cause failures. Avoid using it for critical production scaffolding until you’ve thoroughly tested it in staging. If issues arise, fork the repository to backport fixes or add tests to mitigate risks.
- Can I use this package alongside other scaffolding tools like Laravel Breeze or Jetstream?
- While technically possible, this package is designed as a standalone scaffolding toolkit and may overlap with tools like Breeze or Jetstream. Use it for custom boilerplate (e.g., internal admin panels) rather than replacing existing auth scaffolding. Ensure there are no naming or dependency conflicts by testing both tools in a shared environment.
- What’s the best way to contribute or request features if the package is abandoned?
- Since the package lacks active maintenance, your best options are to fork the repository on GitHub and submit a pull request with your changes or feature requests. Document any undocumented APIs or edge cases you encounter to help future maintainers. Alternatively, reach out to the original author via GitHub issues to discuss adoption or collaboration.