Error : update strapi v4 to v5

[ra-devmaster]

• Node.js version: v20.17.0
• NPM version: 10.8.3
• Strapi version: 4.25.11 to 5.0.0
• Database: "mysql2": "^3.11.1",
• Operating system: LocalHost windows
• Is your project Javascript or Typescript: JS

The bug

Hi,
I managed to upgrade my strapi 4.25.10 to 4.25.11, however when I want to go from v4 to v5 I get this error after running npx @strapi/upgrade major as on the documentation

Screenshots

And on github i have only that change :

After that, if I run npx strapi -v, I'm obviously still in 4.25.11.

[zjjtm]

I got same problem.

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/error-update-strapi-v4-to-v5/47199/1

[derrickmehaffy]

Weird because that package absolutely does exist: https://www.npmjs.com/package/@strapi/plugin-cloud

What is your npm registry set to?

[zjjtm]

Weird because that package absolutely does exist: https://www.npmjs.com/package/@strapi/plugin-cloud

What is your npm registry set to?
npmjs.com

The commentsBot said try to clean the node_modules dir before running the migration script, I did that way but still the error.

[ra-devmaster]

All the minor updates on v4 work, but the problem persists when trying to upgrade to v5. Perhaps --force or --legacy-peer-deps is missing in your script when you're running the installation to avoid the issues we're experiencing here.

I deleted the node_modules folder, but that didn’t help—I’m still getting the error. And if I run npm i, I get the same error.

---

I then tried deleting the node_modules folder and running npm i --legacy-peer-deps. This time, the installations complete but with warnings:

After doing that, I ran npx @strapi/upgrade major and got this message:

But in the end, it doesn’t change anything, and I still have the same error as before.

For your information, I’m working locally, and the site has never been hosted—I started it two weeks ago.

[gbgabo]

@ra-devmaster The warnings regarding packages' vulnerabilities doesn't seem to be inherently a upgrade problem, as I just installed a brand new project (current 5.0.1) and on the process it showed many similar packages warnings. Not sure if it helps for the issue, but just so everybody knows:

Also, coincidentally I was facing the same issue for upgrading and I share the same situation on being a project never deployed and started around 2 weeks.

In my case, conveniently I was able to simply restart a project, as I was still testing a lot with no real data. Hope everything gets solved for you!

[ra-devmaster]

No, nothing works, and even doing a V5 project causes problems.

[abinici]

If you are getting the above npm error, try running the following command:

npm i @strapi/strapi@latest @strapi/plugin-users-permissions@latest

This will install the latest version of the two packages, which should be version 5.0.1. After running this command, I was able to build and run Strapi without any issues.