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 while running npm install #136

Open
CypherPoet opened this issue Mar 27, 2021 · 1 comment
Open

Error while running npm install #136

CypherPoet opened this issue Mar 27, 2021 · 1 comment
Assignees

Comments

@CypherPoet
Copy link

When running npm install using npm 7.5.2 and node v14.16.0, I get the following error:

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!   react@"16.13.1" from the root project
npm ERR!   peer react@"^15.0.0 || ^16.0.0" from @cleandersonlobo/[email protected]
npm ERR!   node_modules/@cleandersonlobo/react-mic
npm ERR!     @cleandersonlobo/react-mic@"^1.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.14.0" from [email protected]
npm ERR! node_modules/react-dom
npm ERR!   react-dom@"^16.9.0" from the root project
npm ERR!   peer react-dom@"^15.0.0 || ^16.0.0" from @cleandersonlobo/[email protected]
npm ERR!   node_modules/@cleandersonlobo/react-mic
npm ERR!     @cleandersonlobo/react-mic@"^1.2.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!

It looks like running npm install --legacy-peer-deps does, indeed, get around this, but I’m curious about the best path forward for the project here. We could try to upgrade react to ^16.4.1, or, if we’re not ready to do that, update the README installation instructions to include the extra --legacy-peer-deps argument.

Related:

@Evanfeenstra
Copy link
Contributor

I guess upgrading to React 16.4.1 is the best path forward, feel free to give it a try :)

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

2 participants