- What is Laravel Zero used for?
- Laravel Zero is a micro-framework for building standalone console applications using a slim subset of Laravel components. It suits internal tooling, ops runbooks, data migration scripts, and scheduled batch jobs where the team already knows Laravel. It is not a web framework and does not provide HTTP routing, sessions, or authentication by default.
- Is nunomaduro/laravel-zero still maintained?
- The nunomaduro/laravel-zero package name is a legacy identifier, and its last release reflects an abandoned package name rather than an abandoned project. Active development moved to laravel-zero/framework and laravel-zero/installer. Any Composer constraint, internal mirror, or SBOM rule pinned to nunomaduro/* should be updated before you start.
- How do I install Laravel Zero?
- Install it with Composer using the current installer, for example composer create-project laravel-zero/installer my-app. Do not install the legacy nunomaduro/laravel-zero package. After scaffolding you get an application skeleton with a console kernel, a commands directory, and a default command ready to extend.
- Which Laravel or Illuminate versions does Laravel Zero support?
- Laravel Zero tracks recent Illuminate major releases through the laravel-zero/framework package, so check that repository for the currently supported major. If your CLI shares internal packages with a full Laravel application, pin the Illuminate constraints to the same major to avoid dependency conflicts. Symfony Console major versions also matter because they can change input and output APIs.
- Can I use Eloquent and a database in Laravel Zero?
- Eloquent is optional in Laravel Zero and can be added when a command needs database access. You configure connections explicitly rather than relying on a full framework bootstrap. Keep credentials and connection settings in config files or environment variables that fit your distribution model.
- How do I test Laravel Zero commands?
- Laravel Zero provides Laravel-style testing ergonomics, so you can extend its TestCase and use artisan-style assertions against your commands. Tests typically run under PHPUnit or Pest and can assert exit codes and console output. Keep command logic in testable classes and use thin command wrappers to make unit testing easier.
- How should I distribute a Laravel Zero CLI application?
- Common distribution models are a PHAR archive built with Box, a Composer global require, or a container image. Laravel Zero includes a self-update mechanism, but you must own the release channel, artifact signing or verification, and an air-gapped fallback. Decide the distribution model early because it affects packaging, config loading, and update behavior.
- Does Laravel Zero support scheduling and queues?
- Laravel Zero includes console scheduling support, so you can define scheduled tasks and run them through the scheduler command. Queues and queue workers are not part of the default slim stack and must be wired manually if needed. If a command depends on HTTP routing, sessions, or auth, Laravel Zero is probably the wrong tool.
- Laravel Zero vs plain Symfony Console: which should I choose?
- Choose Laravel Zero when your team already writes Laravel and you want service providers, config handling, scheduling, and familiar testing in a standalone CLI. Choose plain Symfony Console when you want the smallest dependency surface and do not need Laravel components. A single existing artisan command inside a full Laravel app may also make a separate CLI framework unnecessary.
- What are the main risks of adopting Laravel Zero?
- The highest-severity risk is duplicating domain logic that already lives in your main Laravel application, which can silently diverge over time. You also need to manage Illuminate version alignment, distribution and self-update ownership, and missing full-framework features such as queues or HTTP defaults. Fix legacy package names in tooling and SBOMs before integration.