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

NPM package can't resolve peer-dependencies #468

Open
r-watkins opened this issue May 6, 2021 · 0 comments
Open

NPM package can't resolve peer-dependencies #468

r-watkins opened this issue May 6, 2021 · 0 comments

Comments

@r-watkins
Copy link

Problem

I'm trying to update calcite-react from version 0.58.0 to version 0.59.0. There is a peer-dependency conflict with react. I'm on react version 17.0.2 and the peer-dependency wants me to be at 16.8.2.

Possible Solution

I had a similar issue with one of my npm packages. It was trying to force users to react 16.5.0. I was able to fix it by adjusting the peer-dependency to ">= 16.5.0". A possible fix is to set "react": ">= 16.8.6" in your peer-dependencies.

Context + Screenshots

Here's the error output:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: cui-icons-reference@0.30.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   dev react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.6" from calcite-react@0.59.0
npm ERR! node_modules/calcite-react
npm ERR!   calcite-react@"0.59.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/ryan8609/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ryan8609/.npm/_logs/2021-05-06T19_13_49_199Z-debug.log
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

1 participant