- What is laracademy/generators used for in Laravel?
- Laracademy Generators is a developer-time Artisan scaffolding utility for Laravel. It helps generate models, controllers, migrations, and related classes to reduce repetitive CRUD and boilerplate work. It is best treated as an optional productivity tool rather than a runtime framework dependency.
- How do I install laracademy/generators?
- Install it with Composer, most likely as a dev dependency using composer require --dev laracademy/generators. Then use the Artisan commands provided by the package to scaffold files. Confirm the exact command names and options in the package README before rolling it out to a team.
- Which Laravel and PHP versions does laracademy/generators support?
- The provided context does not list an official Laravel and PHP support matrix. Because the last release was in October 2023, treat compatibility with newer Laravel major versions as unproven until tested. Validate it against your actual Laravel version, PHP version, and Composer dependency set in CI before adoption.
- Should laracademy/generators be a production dependency?
- No. It should be installed as a require-dev package and used only during development. Keeping it out of production limits runtime security exposure and avoids making a scaffolding utility part of your deployed application. Generated code should still be reviewed before it reaches production.
- Can I customize the stubs used by laracademy/generators?
- The package is described as supporting customizable stubs, which is important for matching internal conventions. Check the README and available Artisan commands to confirm how templates can be published or overridden. Teams with strict architecture or naming standards should version their customized stubs internally.
- Does laracademy/generators generate tests, validation, authorization, and relationships?
- The provided context does not confirm that it generates tests, validation, authorization rules, or relationship handling. Evaluate generated output on a representative module before assuming those features are covered. If those elements matter, plan to add them through custom stubs or manual review.
- How does laracademy/generators handle existing files and overwrites?
- Overwrite behavior is not specified in the provided context, so verify it before using the package on important files. Run generation in a clean branch and keep changes under version control so existing code can be reviewed or restored. Treat file overwrite behavior as a guardrail item during any pilot.
- Is laracademy/generators actively maintained?
- It is MIT-licensed and has reasonable community signal for a utility, but the last release in October 2023 suggests limited strategic maturity. Expect community support only, with no SLA from the maintainers. Assign an internal owner to monitor compatibility and be prepared to fork or replace it if it is abandoned.
- What are alternatives to laracademy/generators for Laravel scaffolding?
- Alternatives include Laravel's built-in Artisan make commands, custom internal generators, or other community scaffolding packages. If laracademy/generators fits only partially, extract useful templates into an internal generator rather than forcing adoption. The main decision is whether the generated output matches your team's conventions and review standards.
- How should a team pilot laracademy/generators safely?
- Start with a time-boxed spike in a branch and generate one representative CRUD module. Compare the output against hand-written code, customize stubs if needed, and add a review checklist for generated files. Keep it dev-only, pin the version in composer.lock, and expand only after a small pilot proves useful.