We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 pulling the main branch the npm packages won't install with npm install due to a number of conflicting dependencies around react.
npm install
react
After closer inspection of the failing packages, it turns out that the packages causing the error aren't even in use anywhere. Specifically:
With the changes in this forked branch both npm and yarn are able to complete and run both develop and build successfully.
npm
yarn
develop
build
Still a lot of other outdated packages, etc. but at least it runs.
The text was updated successfully, but these errors were encountered:
Same issue for me as well
npm install throws following error and does not install the reps. Using --legacy-peer-deps also fails.
--legacy-peer-deps
rudderstack-docs $npm install 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@"^17.0.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.13.1" from @mdx-js/[email protected] npm ERR! node_modules/@mdx-js/runtime npm ERR! @mdx-js/runtime@"^1.6.22" 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.
Sorry, something went wrong.
No branches or pull requests
When pulling the main branch the npm packages won't install with
npm install
due to a number of conflicting dependencies aroundreact
.After closer inspection of the failing packages, it turns out that the packages causing the error aren't even in use anywhere. Specifically:
With the changes in this forked branch both
npm
andyarn
are able to complete and run bothdevelop
andbuild
successfully.Still a lot of other outdated packages, etc. but at least it runs.
The text was updated successfully, but these errors were encountered: