Skip to content

Package Issues

If you install a project on your local machine, the project can’t be installed due to errors. These errors are mainly in caused by Strapi V5 packages.

Mostly the solution is to check the package.json for packages using "latest" instead of a version number. Mostly inside the backend or cms folder

  • Check your package.json for any packages using latest instead of a specific version number. Replace latest with a fixed version number. Check list of know packages.
  • Remove docusaurus and all docs references
  • Check your Node.js engine versions and ensure compatibility.
{
"@ef2/content-components-react": "remove this package since it's deprecated",
"@ef2/strapi-plugin-bold-title-editor": "1.0.9",
"@_sh/strapi-plugin-ckeditor": "3.0.0",
"@sklinet/strapi-plugin-video-field": "1.0.5",
"@strapi/plugin-graphql": "4.13.7",
"@strapi/plugin-seo": "1.9.5",
"strapi-plugin-config-sync": "1.2.6",
"strapi-plugin-local-image-sharp": "1.7.0",
"strapi-plugin-navigation": "2.4.0",
"strapi-plugin-placeholder": "4.4.0",
"strapi-plugin-teaser": "0.0.3"
}

Make sure you don’t use the ^ to prevent minor updates
The list above show all the package versions that are before the Strapi V5 update.

If you’re sure that everything works on your local machine (so you can build the project), make sure it also works on Rootnet/Vercel.

Project nameNextJS versionStrapi version
AAGB14.1.44.21.0
Auto Repair Master (ARM)14.2.54.24.2
Banvo14.1.44.21.0
Kentekenloket14.2.54.13.7
Leaseprof14.2.54.20.2
Tech36014.2.54.23.1
Tyres-On14.2.54.24.2
vandervalk+degroot14.1.44.21.0
Project nameNextJS versionStrapi version
Kika13.5.24.10.1