Support the ongoing development of →
posted 1 year ago
Last updated 1 year ago.
moderator Solution

Hello @luca-alsina

I suspect that you had an invalid cache file that has been removed or rewritten after your composer update. Or the opcode cache from PHP or something else was in an invalid state.

ps. For a project it can be a good idea to run composer install on your server and not composer update. That gives you the security that it use the exact versions as found in your composer.lock file. You can update your packages local or with a tool like dependabot, test it and with a new deploy install the new versions.

luca-alsina liked this reply

Solution selected by @luca-alsina

Sign in to participate in this thread!


Your banner here too?


We'd like to thank these amazing companies for supporting us

Your logo here?

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 - All rights reserved.