apollo-client-devtools icon indicating copy to clipboard operation
apollo-client-devtools copied to clipboard

ERESOLVE error when running npm install

Open bignimbus opened this issue 3 years ago • 1 comments

Intended outcome:

Running npm install should result in a successful download and installation of dependencies

Actual outcome:

Running npm install produces the following output:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!   peerOptional react@"^16.8.0 || ^17.0.0" from @apollo/[email protected]
npm ERR!   node_modules/@apollo/client
npm ERR!     @apollo/client@"^3.3.13" from the root project
npm ERR!   27 more (@apollo/space-kit, @emotion/core, @emotion/react, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.3.1 || ^16.0.0" from [email protected]
npm ERR! node_modules/graphql-syntax-highlighter-react
npm ERR!   graphql-syntax-highlighter-react@"^0.4.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^15.3.1 || ^16.0.0" from [email protected]
npm ERR!   node_modules/graphql-syntax-highlighter-react
npm ERR!     graphql-syntax-highlighter-react@"^0.4.0" from the root project
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 /Users/jeffauriemma/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jeffauriemma/.npm/_logs/2022-09-20T03_19_00_983Z-debug-0.log

How to reproduce the issue:

See above

Desktop (please complete the following information):

  • OS: macOS Monterey 12.3
  • main branch

bignimbus avatar Sep 20 '22 03:09 bignimbus

For anyone following this issue, the immediate workaround is to run npm install --force

bignimbus avatar Sep 20 '22 03:09 bignimbus