Composer recently made a change with the way
pre-update-command works and it can cause Laravel to fail to install.
Jordi Boggiano gave the following reason for the change:
as there is no composer.lock file the initial “install” is instead doing an update (as of this afternoon), which triggers the pre-update-cmd, while this was previously triggering pre-install-cmd.
Luckily the fix is easy and only requires a moving the
php artisan clear-compiled to the
You can see the complete changelog here.
Join the weekly newsletter and never miss out on new tips, tutorials, and more.
- Laravel + Vue.JS developer
Remote or in Toronto Canada
Star Dot Hosting Inc
- Full Stack or Back-End Developer
Alexandria, VA; Tallahassee, FL; Orlando, FL
Marketing for Change
- Senior Quality Assurance Engineer
- Senior PHP/Laravel Developer: Your Dream Work Environment
iPhone Photography School
- Senior Software Engineer
Remote or San Francisco
- Laravel Developer
Las Vegas, NV
- R&D Developer
Laracon US Schedule Announced
Laracon just announced the preliminary schedule for this year’s conference. Just as in the past, it leaves ampl…
How To Rescue Legacy Code through Refactoring
Jeroen Moons shares his advice for getting a legacy codebase under control. It’s full of great information, and…