Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laminas Cli

Laminas Cli Laravel Package

laminas/laminas-cli

Console tooling for Laminas applications and components. Provides a CLI entry point, command discovery/registration, and integration helpers to build and run project-specific commands via Composer and your framework configuration.

View on GitHub
Deep Wiki
Context7

Console command runner, exposing commands written in Laminas MVC and Mezzio components and applications

Frequently asked questions about Laminas Cli
Can I use laminas-cli in Laravel projects, or is it only for Laminas/Mezzio?
While laminas-cli is designed for Laminas projects, its core features—like Symfony Console integration and PSR-11 container support—work with Laravel. You can use it for custom CLI tools, especially if you need Laminas-specific integrations or advanced input handling. However, manual setup (e.g., container binding) may be required due to Laravel’s container differences.
How do I install laminas-cli in a Laravel project?
Run `composer require laminas/laminas-cli` to install. However, since Laravel’s container isn’t natively compatible, you’ll need to either wrap it in a PSR-11 container adapter or register commands manually via a Laravel service provider. Check the [README](https://github.com/laminas/laminas-cli) for container configuration options.
Will laminas-cli work with Laravel’s Artisan commands?
No, laminas-cli and Artisan are separate systems, but they can coexist. If you need Laminas-specific CLI features (e.g., advanced input prompts), laminas-cli may complement Artisan. For most Laravel use cases, Artisan alone is sufficient unless you’re bridging Laminas and Laravel ecosystems.
How do I register custom commands with laminas-cli in Laravel?
Bind commands via a Laravel service provider using `$this->app->singleton(MyCommand::class)`. Alternatively, configure them in `config/laminas-cli.php` if you’re using the package’s native setup. Ensure commands are namespaced to avoid conflicts with Artisan (e.g., `laminas:` prefix).
Does laminas-cli support Laravel’s non-interactive environments (e.g., CI/CD)?
laminas-cli’s interactive prompts (e.g., input parameters) may fail in non-interactive contexts like CI. Mitigate this by providing default values or using CLI arguments instead. Test commands in `--no-interaction` mode to ensure compatibility with Laravel’s scheduled tasks or deployments.
What Laravel versions does laminas-cli support?
laminas-cli itself doesn’t enforce Laravel version constraints, but it requires PHP 8.0+ and Symfony Console (v5.4+). Ensure your Laravel version (8.x+) aligns with these dependencies. Test thoroughly, as container integration may vary across Laravel releases.
Can I replace Artisan with laminas-cli entirely in Laravel?
No, laminas-cli isn’t a drop-in replacement for Artisan. While it shares Symfony Console under the hood, it lacks Laravel-specific features like migrations, queues, or Eloquent integrations. Use it only for custom or Laminas-compatible CLI tools alongside Artisan.
How do I handle dependency injection for laminas-cli commands in Laravel?
Laravel’s container (PSR-11) can inject dependencies into laminas-cli commands if registered via a service provider. For example, bind a command’s dependencies manually in `register()` or use Laravel’s autowiring. Avoid relying on laminas-cli’s native container setup to prevent conflicts.
Are there performance concerns with adding laminas-cli to Laravel?
laminas-cli adds minimal overhead if used sparingly for custom commands. However, its Laminas-specific abstractions (e.g., config keys) may introduce slight bloat. Profile your app to ensure no performance degradation, especially in high-traffic CLI workflows like queues or migrations.
What alternatives exist for advanced CLI tooling in Laravel?
For Symfony Console-based CLI tools, consider Symfony’s `console` component directly or packages like `spatie/laravel-command`. If you need Laminas integrations, laminas-cli is unique, but for pure Laravel, Artisan or Symfony’s tools are more idiomatic. Evaluate based on your project’s ecosystem (e.g., Laminas vs. Laravel-only).
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
calmfox/watch-sylius
damienfern/grpc-symfony-bundle
atoolo/index-bundle
atoolo/genai-bundle
coprotoai/laravel-ticket
davidjln/llm-carbon-bundle
cryonighter/valid-request-bundle
coolms/taxonomy-bundle
coolms/field-bundle
articulate-orm/symfony
aaix/laravel-tall-architect
ephoto/akeneo-connector
emmanuelballery/eb-plantumlbundle
emielburgman/symfony-visitor-beacon
emielburgman/symfony-visit-storage
emielburgman/symfony-security-headers
emielburgman/symfony-log-viewer
emarref/xdebug-bundle
emarref/pubnub-bundle
elriseio/finance-money-bundle