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

Update to React 17 Dependency #104

Open
awitherow opened this issue Oct 6, 2021 · 4 comments
Open

Update to React 17 Dependency #104

awitherow opened this issue Oct 6, 2021 · 4 comments
Assignees

Comments

@awitherow
Copy link

awitherow commented Oct 6, 2021

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: my-app@0.1.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@"^0.14.0 || ^15.0.0-0 || ^16.0.0-0" from react-messenger-customer-chat@0.8.0
npm ERR! node_modules/react-messenger-customer-chat
npm ERR!   react-messenger-customer-chat@"*" 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 am doing with legacy peer deps right now but don't want sketch legacy stuff in my prod app.

@belkocik
Copy link

belkocik commented Dec 1, 2021

Yessir! same here. @chentsulin are you going to update to react 17^?

@chentsulin chentsulin self-assigned this Dec 2, 2021
@koutsosg
Copy link

koutsosg commented Dec 19, 2021

Looks like it works with no problem for now when npm installed with --force

@bilal1031
Copy link

Looks like it works with no problem for now when npm installed with --force

I am facing the react 17 dependency issue, tried --force but node does not detect the module package.

I am using node v16 , react v17 for my current project.
Kindly help me with this issue.

@tokomeno
Copy link

tokomeno commented Nov 6, 2022

looks like it works with the latest react, can we update the peer-dependency in package.json? I'm tired of using the --legacy-peer-dep every time I install packages...

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

6 participants