laravel:runner-selection

When Sail is unavailable, Laravel artisan commands fall back to host system PHP and Composer. This ensures your development environment remains functional by executing commands like 'php artisan test' directly on the host instead of using Sail.

Consistent Laravel command execution is achieved by prioritizing Sail for environment standardization. If Sail is missing, it automatically falls back to host PHP, Composer, and Node.js, preventing environment conflicts and streamlining command management.

Yes, the runner supports Node.js and pnpm operations alongside PHP and Composer. It manages command execution for artisan, composer, and pnpm operations across different development setups, ensuring non-interactive command execution regardless of the environment.

Sail command execution fails outside a Sail environment because the Docker containers are not running. This runner solves that by detecting Sail's absence and automatically falling back to host system tools like PHP, Composer, and Node.js.

Yes, you receive safety notes for database-destructive commands. The runner ensures non-interactive command execution while actively identifying and providing safety warnings for operations that might cause database destruction.

You need to use host PHP instead of Sail when the Sail environment is not installed or running. The runner automatically detects this and switches to host system tools, allowing seamless execution of artisan and composer operations.