- What is joshembling/artisan-browse used for?
- It is a developer productivity package for Laravel that lets you discover, search, and inspect Artisan commands and their signatures, arguments, options, and descriptions from an interactive interface instead of memorizing artisan list output. The supplied overview describes it as a terminal UI, while one blurb calls it a web interface, so confirm the exact UI mode in the repository before adopting it. It is intended as a local developer aid, not application runtime infrastructure.
- How do I install Artisan Browse in a Laravel application?
- Install it as a dev dependency with composer require --dev joshembling/artisan-browse, then rely on Laravel package auto-discovery or follow any service-provider registration steps in the README. The exact invocation command is not included in the supplied metadata, so check the package README after installation. Pin the version in composer.json so local environments stay consistent.
- Which Laravel and PHP versions does Artisan Browse support?
- The provided record does not explicitly list a supported Laravel or PHP version matrix. Check the package composer.json on Packagist and the README for require constraints and tested versions before rolling it out. Validate against your organization's supported Laravel and PHP versions in a non-critical repository first.
- Does Artisan Browse work in Docker, SSH, WSL, and Windows terminals?
- Interactive terminal UIs can behave differently across TTY environments, so test the package in each developer setup you support, including Docker-based local stacks, SSH sessions, WSL, and Windows terminals. The TPM assessment flags terminal and TTY behavior as a key compatibility concern. Confirm rendering, keyboard input, and command execution before documenting it for the team.
- Can I run Artisan Browse in CI or a non-interactive shell?
- It is not designed as a CI tool, and interactive terminal UIs commonly fail or hang when stdout is not a TTY. Avoid adding it to CI pipelines or scripts that expect deterministic, non-interactive output. If you need command discovery in automation, use artisan list or a custom script instead.
- Does Artisan Browse protect against destructive commands like migrate:fresh or db:wipe?
- The supplied context does not confirm built-in confirmation, dry-run, or special handling for destructive Artisan commands. Because the tool can execute commands, treat that as a safeguard you must verify in the source and test in a disposable environment. Document safe usage and avoid running it against production databases.
- Should Artisan Browse be installed as a dev dependency only?
- Yes. It is a developer-only productivity tool and should not be part of production runtime dependencies. Install with --dev, keep production Composer installs free of the package where possible, and pin the version. This also limits third-party dependency and supply-chain exposure in production.
- Does Artisan Browse add runtime overhead to my Laravel application?
- It should not affect production request paths, data models, queues, or deployment topology because it is an orthogonal developer aid. If auto-discovery registers a service provider, that overhead applies only where the package is installed, typically local or development environments. Using --no-dev in production keeps it out of the deployed vendor tree.
- Does Artisan Browse require configuration or send telemetry?
- The provided metadata does not document any telemetry, network access, or required config file. Review the package source, composer.json, and README before adopting it in restricted environments. If network access or configuration is required, document it in your internal runbook.
- What are alternatives to Artisan Browse for exploring Laravel commands?
- Built-in artisan list and artisan help show command signatures, arguments, options, and descriptions without an extra dependency. Laravel Tinker and IDE helpers can also speed up command discovery. Artisan Browse adds a searchable interactive layer, so evaluate whether that convenience justifies another dev dependency.