You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
Running npm ci against our current main branch will succeed with npm v8.5.5.
When updating to npm v8.8.0 (I didn't try any of the intermediate versions), it fails with:
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/markdown-it
npm ERR! dev markdown-it@"^12.0.1" from the root project
npm ERR! peer markdown-it@"*" from [email protected]
npm ERR! node_modules/markdown-it-anchor
npm ERR! dev markdown-it-anchor@"^8.1.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer markdown-it@">= 9.0.0 < 12.0.0" from [email protected]
npm ERR! node_modules/markdown-it-attrs
npm ERR! dev markdown-it-attrs@"^3.0.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/markdown-it
npm ERR! peer markdown-it@">= 9.0.0 < 12.0.0" from [email protected]
npm ERR! node_modules/markdown-it-attrs
npm ERR! dev markdown-it-attrs@"^3.0.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.
Presumably this is explained by something in https://github.com/npm/cli/releases, but I'm not sure what at the moment. Ideally, we'll be able to resolve this issue by updating the dependency that's triggering the breakage.
The text was updated successfully, but these errors were encountered:
jeffposnick
added
bug
Something on the site is broken!
P2
A normal priority task. This is the default for most issues.
labels
May 13, 2022
Running
npm ci
against our currentmain
branch will succeed withnpm
v8.5.5.When updating to
npm
v8.8.0 (I didn't try any of the intermediate versions), it fails with:Presumably this is explained by something in https://github.com/npm/cli/releases, but I'm not sure what at the moment. Ideally, we'll be able to resolve this issue by updating the dependency that's triggering the breakage.
The text was updated successfully, but these errors were encountered: