After the version (10.54.3) which did not register developer commands in non local environment, version 10.55.0 extracted all development commands into a separate package (maravel-framework-dev).
By doing this:
- accidental or malicious run of those commands in prod will be prevented (unless the composer install is run without ‘— no-dev’)
- the core lost about ~10.8 k rows of overhead, improving bootstrap speed
- backward compatibility is preserved by running in Maravel/Maravelith:
composer require macropay-solutions/maravel-framework-dev --dev
Challenge:
Will the commands from \Illuminate\Foundation\Providers\ArtisanServiceProvider work if added to \Laravel\Lumen\Console\ConsoleServiceProvider?
UPDATE 2026.01.07
Version 1.1.0 of maravel-framework-dev is auto-registering the missing commands from Maravel/Lumen except for:
event:generate, make:component, stub:publish, vendor:publish, route:list
because they use Illuminate Foundation classes not present in Lumen and not loaded in Maravel.


