It appears from your log that some of the versions of packages that are listed in your composer.lock tệp tin are no longer available. Thus, when you run composer install, it complains và fails. This is usually no big khuyến mãi - just run composer update & it will attempt lớn build a phối of packages that work together và write a new composer.lock file.

Xem thêm:

However, you"re running into a different problem. It appears that, in your composer.json file, the original developer has added some pre- or post- update actions that are failing, specifically a php artisan migrate command. This can be avoided by running the following: composer update --no-scripts

This will run the composer update but will skip over the scripts added khổng lồ the file. You should be able khổng lồ successfully run the update this way.

However, this does not solve the problem long-term. There are two problems:

A migration is for database changes, not random stuff lượt thích compiling assets. Go through the migrations và remove that code from there.

Assets should not be compiled each time you run composer update. Remove that step from the composer.json file.

From what I"ve read, best practice seems to lớn be compiling assets on an as-needed basis during development (ie. When you"re making changes to lớn your LESS files - ideally using a tool like gulp.js) and before deployment.