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
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: [email protected]
npm ERR! Found: [email protected]
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 [email protected]
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
The text was updated successfully, but these errors were encountered:
Problem
I'm trying to update
calcite-react
from version0.58.0
to version0.59.0
. There is a peer-dependency conflict with react. I'm on react version17.0.2
and the peer-dependency wants me to be at16.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:
The text was updated successfully, but these errors were encountered: