- What is nunomaduro/zero-framework and what does it do?
- It is the core Laravel Zero package: a console-first micro-framework that wires illuminate/container, console, config, events, and log into a single-purpose CLI application. It provides the application builder, kernel, bootstrap sequence, and built-in commands such as app:build and app:rename. It is not a full HTTP framework; its value is Laravel-style developer ergonomics for shipped command-line tools.
- How do I install and start a Laravel Zero CLI app with this package?
- Install it as a Composer dependency in a dedicated CLI project, for example with composer require nunomaduro/zero-framework, then define commands using illuminate/console conventions. For a new application, the normal starting point is the Laravel Zero application scaffold rather than adding this core package to an existing Laravel monolith. Keep the CLI as its own repository or artifact so its illuminate/* constraints do not collide with a full Laravel install.
- Which PHP and Laravel versions does zero-framework support?
- The package tracks Laravel's illuminate/* major versions, which ship roughly twice a year. The exact PHP floor and illuminate major are pinned by the specific package release, so inspect that version's composer.json and compare it with your fleet's PHP versions before adopting it. Pinning zero-framework means you inherit that semi-annual upgrade cadence.
- Can I use zero-framework inside an existing Laravel application as a console layer?
- No. This is an application skeleton and core framework for a standalone CLI, not a library you drop into an existing Laravel app. It competes with a full laravel/framework install for the same illuminate/* namespaces and version constraints. Scope it as a separate repository and artifact, never as a module inside the monolith.
- What kinds of projects is Laravel Zero a good fit for?
- It fits shipped command-line tools such as internal build and deploy tooling, data-migration runners, scheduled job wrappers, scaffolding generators, and small daemons. It is a good choice when the team already knows Laravel idioms and wants config, dependency injection, logging, events, and testing ergonomics in a CLI. It is the wrong fit for anything serving HTTP, queue workers at scale, or cases where plain Symfony Console would be sufficient.
- Is Phar distribution mandatory, or can I ship via Composer on managed hosts?
- Phar is the intended distribution path and is well-trodden via Box, giving a single-file artifact that avoids managing a PHP dependency tree on target hosts. It is not strictly mandatory; you can ship via Composer when managed hosts already provide PHP and Composer. Phar packaging adds work around signing, phar.readonly, and CI packaging, so decide based on your target environment.
- How does zero-framework compare to plain Symfony Console?
- Both are console frameworks, but Laravel Zero adds Laravel-style config, dependency injection, logging, events, and testing ergonomics on top of illuminate/console components. The tradeoff is an inherited dependency on illuminate/* and a semi-annual upgrade cadence. Choose Laravel Zero when Laravel familiarity and those defaults buy enough value; otherwise a plain Symfony Console application may be simpler.
- How should I test Laravel Zero commands?
- Laravel Zero is designed for Laravel-style testing ergonomics, so assert command output and exit codes with your preferred PHP test runner such as PHPUnit or Pest. Keep commands small and push logic into testable services wired through illuminate/container. Test the packaging path separately if you ship a Phar, because build and runtime behavior can differ.
- What maintenance and upgrade risks should I plan for?
- The main exposure is dependency coupling: the framework tracks illuminate/* major versions, so a pinned package inherits a semi-annual upgrade obligation. Record the split identity between the laravel-zero GitHub org and the nunomaduro Packagist namespace, and confirm who controls the Packagist entry and what happens on maintainer handover. Assign an owner for upgrade cadence when Laravel ships a new major.
- Why does zero-framework show zero dependents, and does that mean it is not adopted?
- The zero-dependents figure almost certainly counts direct dependents of this exact Composer package name, not overall Laravel Zero adoption. Most consumers pull Laravel Zero through the application scaffold rather than requiring the framework package directly. Do not use that number as an adoption signal in either direction; evaluate fit, maintenance, and provenance instead.