You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new behavior of npm install is to require --force on peer-deps, which causes issue on a project that has other dependencies on a later version of a peer dep (in this case graphql.)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @gummicube/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR! graphql@"^15.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^0.13.2" from [email protected]
npm ERR! node_modules/graphql-type-datetime
npm ERR! graphql-type-datetime@"^0.2.4" 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.
Can you update the peer-dep to graphql@"^15.5.0"? I'm also happy to open a PR, if you don't mind publishing the change.
The text was updated successfully, but these errors were encountered:
The new behavior of
npm install
is to require--force
on peer-deps, which causes issue on a project that has other dependencies on a later version of a peer dep (in this casegraphql
.)Can you update the peer-dep to
graphql@"^15.5.0"
? I'm also happy to open a PR, if you don't mind publishing the change.The text was updated successfully, but these errors were encountered: