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

When react-i18next is updated to 12.0.0, we get npm ERR! ERESOLVE could not resolve on npm install #14

Closed
marcosgilf opened this issue Oct 21, 2022 · 1 comment · Fixed by #15

Comments

@marcosgilf
Copy link
Contributor

marcosgilf commented Oct 21, 2022

When we update react-i18next to latest version 12.0.0, we got the following error on npm install:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: storybook-react-i18next@1.1.2
npm ERR! Found: react-i18next@12.0.0
npm ERR! node_modules/react-i18next
npm ERR!   react-i18next@"12.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-i18next@"^11.17.1" from storybook-react-i18next@1.1.2
npm ERR! node_modules/storybook-react-i18next
npm ERR!   dev storybook-react-i18next@"1.1.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react-i18next@11.18.6
npm ERR! node_modules/react-i18next
npm ERR!   peer react-i18next@"^11.17.1" from storybook-react-i18next@1.1.2
npm ERR!   node_modules/storybook-react-i18next
npm ERR!     dev storybook-react-i18next@"1.1.2" 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.

storybook-react-i18next version 1.1.2

➞ npm -v
8.15.0

➞ node -v
v16.17.0

@marcosgilf marcosgilf changed the title When react-i18next is updated to 12.0.0, we get npm ERR! ERESOLVE could not resolve When react-i18next is updated to 12.0.0, we get npm ERR! ERESOLVE could not resolve on npm install Oct 21, 2022
@sawyerh
Copy link
Contributor

sawyerh commented Dec 5, 2022

This should fix it. #15

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

Successfully merging a pull request may close this issue.

2 participants