"unable to resolve dependency tree" during install

[seancolsen]

When I try to install this project within my Nuxt site, I get the follow error:

npm install --save-dev @nuxtjs/storybook
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   peerOptional react@"^16.8.0 || ^17.0.0" from @storybook/[email protected]
npm ERR!   node_modules/@storybook/addon-essentials
npm ERR!     @storybook/addon-essentials@"^6.1.14" from @nuxtjs/[email protected]
npm ERR!     node_modules/@nuxtjs/storybook
npm ERR!       dev @nuxtjs/storybook@"*" from the root project
npm ERR!   peerOptional react@"^16.8.0 || ^17.0.0" from @storybook/[email protected]
npm ERR!   node_modules/@storybook/addon-actions
npm ERR!     @storybook/addon-actions@"6.1.21" from @storybook/[email protected]
npm ERR!     node_modules/@storybook/addon-essentials
npm ERR!       @storybook/addon-essentials@"^6.1.14" from @nuxtjs/[email protected]
npm ERR!       node_modules/@nuxtjs/storybook
npm ERR!         dev @nuxtjs/storybook@"*" from the root project
npm ERR!   11 more (@storybook/addon-backgrounds, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.4" from [email protected]
npm ERR! node_modules/@storybook/addon-actions/node_modules/react-inspector
npm ERR!   react-inspector@"^5.0.1" from @storybook/[email protected]
npm ERR!   node_modules/@storybook/addon-actions
npm ERR!     @storybook/addon-actions@"6.1.21" from @storybook/[email protected]
npm ERR!     node_modules/@storybook/addon-essentials
npm ERR!       @storybook/addon-essentials@"^6.1.14" from @nuxtjs/[email protected]
npm ERR!       node_modules/@nuxtjs/storybook
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/sean/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/sean/.npm/_logs/2021-03-26T15_12_51_106Z-debug.log

Here's my 'package.json` to show what else I have installed:

{
  "name": "nuxt",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "dev": "nuxt",
    "build": "nuxt build",
    "start": "nuxt start",
    "generate": "nuxt generate",
    "lint:js": "eslint --ext \".js,.vue\" --ignore-path .eslintignore .",
    "lint:fix": "eslint --ext \".js,.vue\" --fix --ignore-path .eslintignore .",
    "lint": "npm run lint:js",
    "cy:open": "cypress open",
    "cy:run": "cypress run"
  },
  "dependencies": {
    "@nuxt/utils": "^2.15.2",
    "@nuxtjs/auth-next": "5.0.0-1613647907.37b1156",
    "@nuxtjs/axios": "^5.13.1",
    "@nuxtjs/universal-storage": "^0.5.7",
    "core-js": "^3.8.3",
    "dotenv": "^8.2.0",
    "nuxt": "^2.14.12",
    "vue": "^2.6.12",
    "vue-debounce": "^2.6.0",
    "vuex": "^3.6.2"
  },
  "devDependencies": {
    "@nuxtjs/eslint-config": "^5.0.0",
    "@nuxtjs/eslint-module": "^3.0.2",
    "@nuxtjs/toast": "^3.3.1",
    "babel-eslint": "^10.1.0",
    "blunt-css": "^1.1.0",
    "cypress": "^6.6.0",
    "eslint": "^7.18.0",
    "eslint-config-airbnb-base": "^14.2.1",
    "eslint-config-standard": "^16.0.2",
    "eslint-plugin-cypress": "^2.11.2",
    "eslint-plugin-import": "^2.22.1",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-nuxt": "^2.0.0",
    "eslint-plugin-promise": "^4.3.1",
    "eslint-plugin-standard": "^4.1.0",
    "eslint-plugin-vue": "^7.7.0",
    "nuxt-purgecss": "^1.0.0"
  }
}

[farnabaz]

This is the issue with NPM modern peed dependency system, Until the fix, try using legacy peer dependency

npm install @nuxtjs/storybook --legacy-peer-deps

[bartenra]

Having the same issue with Vue 3.

I cannot run npm install anymore.

[htlili]

Having same error with react 17. The weird part is that yarn works but npm i does not.

[krutoo]

same issue

[andrew-boyd]

Adding my hat to the ring here - same issue with npm i

[tobiasdiez]

v4 of this module is no longer actively supported. Please try the newest version and open an new issue if the problem persists. Thank you for your understanding.