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

Error when doing npm install for most recent React version #25

Closed
giavinh79 opened this issue Oct 16, 2022 · 3 comments
Closed

Error when doing npm install for most recent React version #25

giavinh79 opened this issue Oct 16, 2022 · 3 comments

Comments

@giavinh79
Copy link

Description

When running npm install react-plock I get the following error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: project@1.0.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.1.0" from react-plock@2.0.0
npm ERR! node_modules/react-plock
npm ERR!   react-plock@"*" 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.

I'm currently on version 18.2.0 of React which is why this is erroring. I believe to fix this, the related dependencies just need to be updated.

Thanks!

@eiiot
Copy link

eiiot commented Jan 30, 2023

+1

@mrLuisFer
Copy link

mrLuisFer commented Feb 26, 2023

Same issue using React v17.0.2

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: project@1.2.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.1.0" from react-plock@2.0.0
npm ERR! node_modules/react-plock
npm ERR!   react-plock@"*" 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!

@askides
Copy link
Owner

askides commented Mar 3, 2023

Hello Guys,

Please check out the new v3.0.0 version just published. In addition to a number of performance and bundle size improvements, the problem you reported has been fixed.

@askides askides closed this as completed Mar 3, 2023
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

4 participants