rudderstack-docs icon indicating copy to clipboard operation
rudderstack-docs copied to clipboard

Main branch has npm dependency issues and won't install / run / build

Open maximum-pixels opened this issue 2 years ago • 1 comments

When pulling the main branch the npm packages won't install with npm install due to a number of conflicting dependencies around react.

After closer inspection of the failing packages, it turns out that the packages causing the error aren't even in use anywhere. Specifically:

  • "@mdx-js/runtime": "^1.6.22"
  • "gatsby-plugin-use-query-params": "^1.0.1"
  • "react-katex": "^2.0.2"
  • "react-rangeslider": "^2.2.0"
  • "react-scroll-up-button": "^1.6.4"

With the changes in this forked branch both npm and yarn are able to complete and run both develop and build successfully.

Still a lot of other outdated packages, etc. but at least it runs.

maximum-pixels avatar Oct 30 '23 13:10 maximum-pixels

Same issue for me as well

npm install throws following error and does not install the reps. Using --legacy-peer-deps also fails.

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.

gitcommitshow avatar Feb 28 '24 18:02 gitcommitshow