Weave Code
Cli Laravel Package
brewless/cli
Brewless CLI is a lightweight command-line toolkit for Laravel and PHP projects, offering simple helpers for building interactive Artisan commands, formatting output, and streamlining developer workflows without extra dependencies.
brewless/cli is a lightweight command-line toolkit for Laravel and PHP projects, built to streamline common development tasks through a clean, expressive terminal interface. It integrates smoothly with Artisan and Symfony Console, making it easy to add custom commands, interactive prompts, and automation to your workflow.
- Artisan-ready commands for quick scaffolding and project tasks
- Interactive prompts for safer, guided input
- Composable command structure for reusable CLI logic
- Framework-friendly integration with Laravel and PHP apps
- Minimal dependencies and straightforward configuration
Frequently asked questions about Cli
- What is brewless/cli and what does it do?
- Brewless CLI is a Composer package that provides a lightweight command-line companion for Laravel and PHP projects. It bundles terminal commands for scaffolding, inspecting, and managing an application, and is designed to be simple and extensible. It fits into existing workflows rather than replacing Laravel Artisan or your current scripts.
- How do I install brewless/cli in a Laravel project?
- Install it with Composer, usually as a development dependency: composer require --dev brewless/cli. In Laravel, follow the README registration steps if the package is not auto-discovered; in plain PHP projects, invoke the provided binary. After installation, list the available commands to confirm it is working.
- Does brewless/cli work with plain PHP projects or only Laravel?
- Brewless CLI is described as a companion for both Laravel and PHP projects, so it is not limited to Laravel. Laravel integration may add convenience such as command registration or framework-aware helpers. In plain PHP projects you would typically use the package binary or Composer scripts. Check the README for the exact entry point.
- Which Laravel versions does brewless/cli support?
- The README and composer.json are the authoritative source for supported Laravel and PHP versions, because the package overview does not list version constraints. Check those constraints against your application's Laravel and PHP versions before installing. If you are on an older Laravel release, test in a branch or CI environment first. Composer will also refuse installation when platform requirements conflict.
- How do I add my own custom commands to brewless/cli?
- The package is described as extensible, so custom commands should follow its documented command structure and registration mechanism. Start by reviewing the source for existing command classes and how they are registered. Then add your own command class and wire it into the package command registration or configuration. Keep custom commands in your application or a separate package to avoid forking unless necessary.
- Is brewless/cli safe to use in production?
- Brewless CLI is a command-line tool, so it does not add runtime overhead to web requests unless you invoke it. Because it includes scaffolding and management commands, install it as a development dependency and avoid exposing it to untrusted users. Review what each command changes before running it against production data, and take backups for destructive operations. Use your normal deployment and access controls.
- How do I test commands from brewless/cli?
- Test package commands the same way you test Artisan or console commands: instantiate the command, run it with a command tester or Laravel test helpers, and assert output and side effects. Use a temporary directory or test database for commands that write files or modify data. Keep tests isolated so scaffolding commands do not touch real application files. Check the package test suite for examples.
- What are the alternatives to brewless/cli?
- Alternatives depend on what you need: Laravel Artisan and Composer scripts cover many built-in tasks, while packages such as Laravel Pint, PHPStan, and Pest handle specific inspection or quality workflows. Brewless CLI's value is bundling scaffolding, inspection, and management commands in one lightweight, extensible tool. Compare command coverage, Laravel version support, and maintenance activity before choosing.
- Is brewless/cli actively maintained?
- Maintenance should be verified from the GitHub repository by checking recent commits, tagged releases, and issue activity. The package is small and lightweight, so release frequency may be lower than large frameworks. For production use, pin a tested version in composer.json and review changes before upgrading. If the project appears inactive, consider whether you can fork or vendor it.
- Can I use brewless/cli alongside Laravel Artisan and Composer scripts?
- Yes, Brewless CLI is intended to fit into existing workflows, so it should complement rather than replace Artisan and Composer scripts. You can call its commands directly, through Composer scripts, or alongside Artisan commands depending on how it is registered. Keep command names distinct to avoid confusion in your terminal workflow. Check the README for the recommended invocation style.
Weaver
How can I help you explore Laravel packages today?