-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.5] Removed optimize command #20771
Conversation
It is being deprecated for one release, according to laravel/ideas#383 |
It is not a breaking change (since it won't destroy any codebase) and it isn't really deprecated. It is softly removed currently, which makes no sense whatsoever. |
We'll remove it in 5.6 and note in the upgrade guide for 5.5. It can break deployment scripts that are calling it if we remove it without warning. |
What about making it write to the console?:
|
Can somebody explain why this was deprecated and what is alternative? |
@decadence i think I remember Taylor maybe saying on a podcast that due to performance improvements in PHP itself (OPCache and whatnot) the command didn't really have any benifit anymore. Don't quote me on that... |
@timacdonald thanks |
so.. should we still using config:cache, route: cache.. ? |
I've just created a new laravel 8.1 through laravel installer, and "artisan optimize" is in the command list |
Removed optimize command, since it was left empty anyway. Closes #20767