Error on strapi upgrade to v4.7.0

System Information
  • Strapi Version: 4.7.0
  • Operating System: MacOs
  • Database:
  • Node Version: 16.15
  • NPM Version: 8.11.0
  • Yarn Version: 1.22.19

Hello,
I have an error when I strapi build :

Building your admin UI with development configuration...
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:372:5)
    at validateString (node:internal/validators:120:11)
    at Object.resolve (node:path:1098:7)
    at /Users/ludgourdon/workspace/cms-v3/node_modules/@strapi/admin/utils/create-cache-dir.js:82:33
    at Array.filter (<anonymous>)
    at createCacheDir (/Users/ludgourdon/workspace/cms-v3/node_modules/@strapi/admin/utils/create-cache-dir.js:80:6)
    at async Object.build (/Users/ludgourdon/workspace/cms-v3/node_modules/@strapi/admin/index.js:27:3)
    at async module.exports (/Users/ludgourdon/workspace/cms-v3/node_modules/@strapi/strapi/lib/commands/build.js:12:3) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Here is my package.json :

{
  "name": "cms-v-3",
  "private": true,
  "version": "0.1.0",
  "description": "xxx",
  "scripts": {
    "develop": "strapi develop",
    "start": "strapi start",
    "build": "strapi build",
    "strapi": "strapi",
    "test": "jest --runInBand"
  },
  "dependencies": {
    "@ckeditor/strapi-plugin-ckeditor": "^0.0.5",
    "@fortawesome/fontawesome-svg-core": "^6.2.1",
    "@fortawesome/react-fontawesome": "^0.2.0",
    "@strapi/plugin-color-picker": "^4.7.0",
    "@strapi/plugin-graphql": "^4.7.0",
    "@strapi/plugin-i18n": "^4.7.0",
    "@strapi/plugin-seo": "^1.7.7",
    "@strapi/plugin-users-permissions": "^4.7.0",
    "@strapi/strapi": "^4.7.0",
    "pg": "^8.6.0",
    "sharp": "^0.31.1",
    "slugify": "^1.6.5",
    "strapi-plugin-populate-deep": "^2.0.0",
    "strapi-plugin-sitemap": "^2.0.8",
    "strapi-provider-upload-wizbii": "file:providers/strapi-provider-upload-wizbii"
  },
  "devDependencies": {
    "@types/jest": "^29.2.3",
    "@types/node": "^18.11.9",
    "@typescript-eslint/eslint-plugin": "^5.45.0",
    "@typescript-eslint/parser": "^5.45.0",
    "eslint": "^8.28.0",
    "eslint-config": "^0.3.0",
    "jest": "^29.3.1",
    "sqlite3": "^5.1.2",
    "supertest": "^6.3.1",
    "ts-jest": "^29.0.3",
    "typescript": "^4.9.3"
  },
  "author": {
    "name": "A Strapi developer"
  },
  "strapi": {
    "uuid": "d4b30970-0d5d-4422-9c7e-c92bb7930126"
  },
  "engines": {
    "node": ">=14.19.1 <=18.x.x",
    "npm": ">=6.0.0"
  },
  "license": "MIT"
}

I forgot to mention that everything was right before I upgrade from strapi 4.6.1 to 4.7.0…

Any ideas please ?

Check the backtrace and look for a line for a file from your code, as opposed to stuff from node_modules or node internals. If you don’t see that then check for the last call to strapi internals and try figure out where it’s getting its data from - in this case I can see:

So check line 82 of that file - It looks like strapi is calling one of node’s path functions with a parameter in an unexpected format - which is probably got from one of your configuration files.

Indeed I had a problem of format in the plugins file ! Thanks !