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

Support react 17 #1662

Closed
Bajdzis opened this issue Oct 11, 2021 · 3 comments
Closed

Support react 17 #1662

Bajdzis opened this issue Oct 11, 2021 · 3 comments
Labels
conflicting dependencies pending-release Issue fixed but not published to npm yet

Comments

@Bajdzis
Copy link

Bajdzis commented Oct 11, 2021

Currently, if we install the docz, we will get an error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: test@1.0.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@"^16.8.0" from docz@2.3.1
npm ERR! node_modules/docz
npm ERR!   docz@"*" 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.

@designbyadrian
Copy link

For those who encounter the error and don't know how to proceed, the temp fix is to bypass the peer installation effort:

npm install docz --save --legacy-peer-deps

This tells the installer to ignore trying to install an older version of react and react-dom on top of the recent version your project has.

But it's likely you're running a later version of Node as well, so this issue will probably be the next thing you'd have to look at: "ERR_REQUIRE_ESM error on start" #1674

@prma85
Copy link
Contributor

prma85 commented Jan 13, 2022

Created a PR to fix it. Let wait for the mainteners
#1692

@renatobenks
Copy link
Member

fixed by #1692

@renatobenks renatobenks added the pending-release Issue fixed but not published to npm yet label Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflicting dependencies pending-release Issue fixed but not published to npm yet
Projects
None yet
Development

No branches or pull requests

5 participants