Laravel Base – A Laravel package that scaffolds a complete API module with one Artisan command

[MuhammedMSalama]

Laravel Base – Generate a Complete Laravel API Module with a Single Artisan Command

Hi Laravel community 👋

Over the last few weeks I've been working on an open-source package called Laravel Base to remove one of the most repetitive parts of starting a new Laravel project.

Instead of creating every layer manually, you can generate an entire production-ready module with a single command:

php artisan make:module Product

The package generates:

• Models
• Migrations
• Repository & Service layers
• Interfaces
• Form Requests
• API Resources
• Filters & Pagination
• Policies
• Status Enums
• Swagger/OpenAPI annotations
• Feature & Unit Tests

The goal isn't to replace Laravel conventions—it's to automate the repetitive boilerplate while keeping the generated code clean, readable, and easy to customize.

Some highlights:

• Supports Laravel 10, 11, 12 and 13
• PHP 8.1–8.4 compatible
• Repository + Service architecture
• Built-in API response helpers
• CI tested across multiple Laravel and PHP versions
• PHPStan & Laravel Pint ready

Repository:

https://github.com/MuhammedMSalama/LaravelBase

Packagist:

https://packagist.org/packages/muhammedsalama/laravel-base

I'd really appreciate feedback from experienced Laravel developers.

If you think something could be improved—or if there's a feature you'd like to see—I'd love to hear your thoughts.

Thanks!

[shaedrich]

Would it make sense to configure which files one wants generated rather than on each command invocation? Otherwise 👌🏻

[MuhammedMSalama]

That's a great suggestion, thanks @shaedrich !

I actually considered a configuration-driven approach. I chose command-line flags (--only, --except, and --no-*) because they're explicit and make each generation command self-contained and reproducible, which is helpful for teams and CI workflows.

That said, I think a global configuration could be a nice addition for developers who consistently generate the same subset of files. A possible approach would be to use configuration as the default and still allow command-line options to override it on a per-command basis.

I'll definitely consider adding this in a future release. Thanks for the feedback!