- How do I install jonpurvis/laravel-uninspire?
- Run composer require jonpurvis/laravel-uninspire in your Laravel project. Laravel package auto-discovery should register the service provider, so no manual provider entry is normally needed. After installation, run php artisan uninspire to confirm the command is available.
- What does the php artisan uninspire command do?
- It generates a random humorous, un-inspirational quote from the console. It is a playful counterpart to Laravel's built-in inspire command. The command does not modify application data or configuration.
- Which Laravel versions are supported by laravel-uninspire?
- The package is Laravel-specific, but the provided evaluation does not confirm exact Laravel constraints. It notes that v3 likely supports Laravel 11 and 12 and may drop older versions. Always check the require block in the package composer.json and the changelog before upgrading.
- What PHP version does laravel-uninspire v3.0.0 require?
- The v3.0.0 release drops PHP 8.2 support, and the evaluation indicates the new baseline is likely PHP 8.3 or higher. Check the exact require constraint in composer.json before installing. If you are on PHP 8.2, stay on v2.0.1 or upgrade PHP first.
- Can I use laravel-uninspire on PHP 8.2?
- No for v3.0.0: that release drops PHP 8.2 support, so Composer will not resolve the package on a PHP 8.2 runtime. You can pin to v2.0.1 if you must stay on PHP 8.2, or upgrade your local, CI, and production environments to PHP 8.3 or higher before adopting v3.
- What breaking changes are in laravel-uninspire v3.0.0?
- The main documented breaking change in v3.0.0 is dropping PHP 8.2 support. The evaluation does not identify other breaking changes, but you should review the changelog and composer.json for the exact PHP and Laravel constraints. Functional behavior of the uninspire command is expected to remain the same.
- How do I migrate from laravel-uninspire v2.0.1 to v3.0.0?
- First upgrade all environments, including local, CI, staging, and production, to PHP 8.3 or higher where required. Then update the package to v3.0.0 with Composer, run your test suite, and smoke-test php artisan uninspire. If you cannot upgrade PHP, pin to v2.0.1 and defer the migration.
- Does laravel-uninspire replace Laravel's built-in inspire command?
- The package is positioned as the opposite of Laravel's inspire command and adds its own uninspire command. The evaluation notes it likely disables or replaces the inspire command, but the public description focuses on adding uninspire. Verify the actual command behavior in your app after installation.
- Is laravel-uninspire safe for production use?
- It is a small, non-performance-sensitive Artisan utility, so runtime risk is low once installed. The main production concern is dependency resolution: ensure production and CI PHP versions meet the v3 requirement. Pin the package version and verify command behavior in staging before deploying.
- How is laravel-uninspire maintained and supported?
- It is a community-supported Laravel package with a narrow scope, so ongoing package maintenance is relatively low. The PHP 8.2 drop may create support questions for teams on older runtimes. Track PHP EOL dates and Laravel's support policy, and keep v2.0.1 as a fallback if needed.