- What is justinbyrne/extra-artisan-commands used for?
- justinbyrne/extra-artisan-commands is a Laravel package that adds extra Artisan commands for everyday development and maintenance chores. It is console-only tooling, so it does not affect HTTP requests, middleware, queues, or your domain model. The exact command list is not documented in the provided context, so inspect it after install before relying on it.
- How do I install justinbyrne/extra-artisan-commands in Laravel?
- Install it with composer require justinbyrne/extra-artisan-commands. On Laravel 5.5 and later, package auto-discovery should register the service provider without edits to config/app.php. If auto-discovery is disabled, register the package provider manually, then run php artisan list to confirm the commands appear.
- Is extra-artisan-commands compatible with Laravel 11 and Laravel 12?
- Compatibility with Laravel 11 and Laravel 12 is unverified: the last release was 2023-06-29, which predates both. Do not trust README version claims alone. Test on a scratch branch with your actual Laravel and PHP versions, run composer why-not, and confirm a clean install resolves before adopting it.
- What PHP and Laravel versions does justinbyrne/extra-artisan-commands require?
- The provided context does not state the exact illuminate/* or PHP constraints. Check the package composer.json for its require block and compare it with your application's Laravel and PHP versions. A composer why-not justinbyrne/extra-artisan-commands check will show what blocks resolution.
- Do I need to register a service provider or publish config for extra-artisan-commands?
- As far as the package surface suggests, there is no persistent configuration file to publish and no bootstrapping change needed on Laravel 5.5+. It contributes commands through a service provider, typically via auto-discovery. Confirm this in the package source if you need certainty for your deployment.
- How can I see which Artisan commands the package adds?
- Run php artisan list before installing and again after, then diff the output to see exactly which commands were added. You can also inspect the installed package source under vendor/justinbyrne/extra-artisan-commands. Classify each command as read-only or mutating before anyone runs it.
- Are the extra Artisan commands safe to run in production?
- Treat production use as a change-control decision, not a default. Command packs of this genre can mix harmless inspectors with generators or data-affecting operations, and the full inventory is not documented here. Prefer require-dev where possible, or document an explicit allowlist of approved commands in the runbook and test mutating commands against a throwaway database first.
- Can package commands conflict with my own custom Artisan commands?
- Yes, custom Artisan commands share the global command namespace, so a package command can collide with or be shadowed by an in-house command with a similar name. Audit the package command names against your app/Console/Commands library before rollout. Rename or avoid conflicting commands if you keep the package.
- Is justinbyrne/extra-artisan-commands actively maintained and tested?
- Maintenance risk is the main concern: the last release was June 2023, it has a single maintainer and modest adoption, and there is no visible corporate backing. Check whether a test suite and CI run against multiple Laravel majors before depending on upstream fixes. If the package goes dormant, plan for a fork or replace commands with native Artisan features.
- How do I uninstall extra-artisan-commands, and is rollback safe?
- Remove it with composer remove justinbyrne/extra-artisan-commands; the integration is purely additive, so rollback is usually that simple. There are typically no migrations or schema changes to undo. If only developers need the commands, install it under require-dev to keep production dependencies smaller.