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

Deps can not be installed with latest npm version 8.11.0 #79

Closed
prince-chrismc opened this issue Jun 1, 2022 · 1 comment · Fixed by #80
Closed

Deps can not be installed with latest npm version 8.11.0 #79

prince-chrismc opened this issue Jun 1, 2022 · 1 comment · Fixed by #80
Labels
bug Something isn't working triage This is a new issue that needs to be reviewed at our Sprint Planning website An issue related to content posted on the website

Comments

@prince-chrismc
Copy link
Contributor

prince-chrismc commented Jun 1, 2022

//cc @efrisch

It works for me installing the current nodejs with npm version 8.5.5 included... it breaks with newer versions

 ✘ christopherm@christopherm-mac  ~/pyrsia-website   main  sudo npm install -g npm@latest

removed 6 packages, changed 74 packages, and audited 202 packages in 3s

11 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
 christopherm@christopherm-mac  ~/pyrsia-website   main  npm i                        
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/mermaid
npm ERR!   mermaid@"^8.14.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mermaid@">= 8.11.0 < 8.12.0" from [email protected]
npm ERR! node_modules/mdx-mermaid
npm ERR!   mdx-mermaid@"^1.2.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/mermaid
npm ERR!   peer mermaid@">= 8.11.0 < 8.12.0" from [email protected]
npm ERR!   node_modules/mdx-mermaid
npm ERR!     mdx-mermaid@"^1.2.3" 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! 
npm ERR! See /Users/christopherm/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/christopherm/.npm/_logs/2022-06-01T18_06_42_035Z-debug-0.log
@prince-chrismc prince-chrismc added the bug Something isn't working label Jun 1, 2022
@github-actions github-actions bot added triage This is a new issue that needs to be reviewed at our Sprint Planning website An issue related to content posted on the website labels Jun 1, 2022
@prince-chrismc
Copy link
Contributor Author

prince-chrismc commented Jun 1, 2022

Digging into this, https://github.com/npm/cli/blob/latest/CHANGELOG.md#bug-fixes-5 has

18b8b9435 npm/cli#4617 fix(arborist): make sure resolveParent exists before checking props (@nlf)

Which makes our current dep tree break

Running npm i -f is enough to bypass the problem


There is actually a problem sjwall/mdx-mermaid@0746bc3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This is a new issue that needs to be reviewed at our Sprint Planning website An issue related to content posted on the website
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant