Weave Code
Code Generator Laravel Package
jtc-solutions/code-generator
A Laravel package for generating code scaffolding, helping you quickly create boilerplate classes and files from customizable templates so you can spend less time on repetitive setup and more on building features.
At a glance
Frequently asked questions about Code Generator
- How do I install jtc-solutions/code-generator in a Laravel app?
- Install it as a development dependency with composer require --dev jtc-solutions/code-generator. Then publish the package config and stubs using Laravel's vendor:publish command, and run the provided Artisan generator commands. Because it writes code at development time, keep it out of production requirements.
- Which Laravel and PHP versions does this code generator support?
- The package overview does not publish a formal Laravel or PHP support matrix, so check the repository's composer.json before adopting it. With a 0.1.x release and no meaningful public adoption, test generation in a disposable branch on your target Laravel version. Pin the exact version rather than relying on a broad constraint.
- How do I publish and customize the stub templates?
- Publish the package's config and stub templates through Laravel's vendor:publish workflow, then edit the published stubs to match your conventions. The publishable config lets you tailor output paths and namespaces without changing vendor files. Commit your customized stubs so generated code stays consistent across the team.
- Can it generate services and repositories as well as models and controllers?
- Yes. The v0.1.2 release expands generation to services and repositories in addition to models, controllers, and other boilerplate. That means the tool encodes a controller-to-service-to-repository layering opinion, so confirm it matches your architecture before using it. Check whether namespaces, base classes, interfaces, and dependency-injection registration are configurable.
- Does the package respect PSR-4 namespaces and custom app paths?
- The package describes PSR-4-aware class and namespace resolution plus publishable config for paths and namespaces. Verify that generated namespaces match your application's autoload configuration, especially if you use a custom app namespace. Generate one class in a test branch and inspect the namespace and file path before rolling it out.
- Will the generator overwrite existing files without confirmation?
- The evaluation flags destructive file operations as a real risk, and the package's overwrite behavior is not confirmed in the provided overview. Before relying on it, run generators in a clean branch with committed work and inspect the diff. If it overwrites silently, add a workflow that backs up or reviews changes before merging.
- Is jtc-solutions/code-generator safe to use in production?
- It is a development-time scaffolding tool, so install it with --dev and keep it out of production dependencies. Generated code becomes your code and your maintenance burden, so review it like any pull request. Also pin versions and review Composer scripts and service providers because dev dependencies still execute on developer machines and CI.
- How do I test generated scaffolding before committing?
- Run the generator in a disposable branch, inspect the generated diff, and execute your normal quality gates such as Pint, PHPStan or Larastan, and Pest or PHPUnit. Since the package does not guarantee tested output, add or update tests for the generated classes. Compare the result against your house conventions before committing.
- What are the alternatives to this Laravel scaffolding package?
- The baseline alternatives are Laravel's built-in make:* Artisan commands combined with your own published stubs. Evaluate any community generator against the same criteria: configurable stubs, PSR-4 correctness, overwrite safety, and whether it encodes a layering pattern you actually use. If your conventions are simple, native Artisan plus custom stubs may be lower risk.
- How actively maintained is it and how should I handle version constraints?
- The recent v0.1.2 release is a positive continuity signal, but the package has a single vendor and essentially no public adoption or issue history. A behavioral change to generated DTO output shipped in a patch-numbered release, which suggests loose versioning discipline. Pin an exact version and review changelogs before upgrading.
Weaver
How can I help you explore Laravel packages today?