Weave Code
Laravel Somake Laravel Package
soyhuce/laravel-somake
A small Laravel package from Soyhuce that adds handy Artisan make commands, streamlining code generation so you can scaffold classes and boilerplate quickly and keep new files consistent with your project's conventions.
An opinionated package to generate classes in your Laravel project
Frequently asked questions about Laravel Somake
- How do I install soyhuce/laravel-somake in a Laravel project?
- Install it as a development dependency with composer require --dev soyhuce/laravel-somake. The package is auto-discovered through its Laravel service provider, so no manual registration in config/app.php is required. If the package ships publishable config or stub files you want to customize, run php artisan vendor:publish for the relevant tag after installing. Commit the composer.json and lockfile changes so everyone on the team gets the same generators.
- What Artisan make commands does laravel-somake add?
- The package adds opinionated Artisan generators on top of Laravel's make:* family, aimed at scaffolding classes and boilerplate that match your project's conventions. Because the command list can change between versions, run php artisan list and check the README for the exact signatures in the version you install. Each command typically accepts a class name and writes a file into the conventional namespace and directory.
- Is soyhuce/laravel-somake a production dependency or dev-only?
- It is development-time tooling, so it belongs in require-dev and should never be part of a production build artifact. It influences developer ergonomics and code-generation consistency rather than request handling, persistence or queue behaviour. Keeping it out of require means production deployments are unaffected if the package is removed or upgraded.
- Does laravel-somake support Laravel 12?
- Release 3.1.0 changes only CI and Dependabot configuration, and its notes state that tests now run with Laravel 12. That signals compatibility but does not by itself prove the published composer.json widens its illuminate/* constraint to ^12.0. Check the constraint before relying on it, because a green CI matrix with a capped constraint will still produce a resolver conflict in a Laravel 12 application.
- How do I upgrade soyhuce/laravel-somake to 3.1.0?
- Bump the constraint to ^3.1 and run composer update soyhuce/laravel-somake --with-dependencies. Release 3.1.0 documents no API changes and no deprecations, so the upgrade is effectively a no-op for existing consumers. Confirm the lockfile only moves this package and its CI-only dependencies, then run your test suite as a smoke check.
- Can I customize the stubs and configuration laravel-somake generates?
- Where the package exposes publishable stubs or config, publish them and keep the overrides under version control so generated classes stay consistent with your conventions. Track those files deliberately, because local customizations can drift when the package updates its defaults. Re-check published assets after each upgrade and diff them against the new vendor versions.
- What PHP and Laravel versions does laravel-somake require?
- The authoritative answer is the illuminate/* and php constraints in the package's composer.json plus its CI matrix; the changelog alone does not disclose the full supported set. The 3.1.0 release indicates Laravel 12 is now exercised in tests, and a PHP 8.2+ baseline with Laravel 10, 11 or 12 is the realistic fit. Verify the matrix matches your application baseline before adding it to your standard scaffold.
- Will laravel-somake conflict with other dev dependencies like PHPUnit or Pint?
- It can. Because the package lives in require-dev, an incompatible illuminate/* constraint blocks resolution of the entire dev dependency graph, including PHPUnit, Pint and static analysis tooling. Test the update on a scratch branch before merging so an unrelated tooling upgrade is not stalled by a constraint conflict.
- Is soyhuce/laravel-somake actively maintained and safe for long-term use?
- Assess release cadence, open issue count and the number of active maintainers, since bus factor matters for a tool baked into your scaffolding. Also look at how quickly the package has supported previous Laravel majors, which is a better predictor than any single release. Note that 3.1.0 contained no package source changes, only Dependabot and CI updates, so it is a compatibility signal rather than a feature release.
- What are the alternatives to soyhuce/laravel-somake for generating Laravel classes?
- Alternatives include Laravel's built-in make commands combined with php artisan stub:publish for customized stubs, hand-rolled generators committed into your application, or other class-generation packages with different opinions. Choose based on how closely a package's conventions match your existing namespaces, directory layout and test scaffolding. laravel-somake fits teams that already standardize on artisan make:* scaffolding and want reusable, opinionated generators.
Weaver
How can I help you explore Laravel packages today?