Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

peer dep on old graphql #4

Open
konsumer opened this issue Feb 25, 2021 · 1 comment
Open

peer dep on old graphql #4

konsumer opened this issue Feb 25, 2021 · 1 comment

Comments

@konsumer
Copy link

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/store@0.2.14
npm ERR! Found: graphql@15.5.0
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 graphql-type-datetime@0.2.4
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.

@saurabh-codeword
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants