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
$ \rm -fr node_modules
$ git branch
...
* main
...
$ git pull
Already up to date.
$ npm -v
8.7.0
$ node -v
v16.14.2
$ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: eslint-config-standard@16.0.3
npm ERR! Found: eslint@8.3.0
npm ERR! node_modules/eslint
npm ERR! dev eslint@"8.3.0" from the root project
npm ERR! peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.16.3
npm ERR! node_modules/@babel/eslint-parser
npm ERR! dev @babel/eslint-parser@"7.16.3" from the root project
npm ERR! 6 more (eslint-config-prettier, eslint-plugin-es, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.12.1" from eslint-config-standard@16.0.3
npm ERR! node_modules/eslint-config-standard
npm ERR! dev eslint-config-standard@"16.0.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR! peer eslint@"^7.12.1" from eslint-config-standard@16.0.3
npm ERR! node_modules/eslint-config-standard
npm ERR! dev eslint-config-standard@"16.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.
npm ERR!
npm ERR! See /Users/kieffer/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/kieffer/.npm/_logs/2022-05-13T19_30_30_624Z-debug-0.log
The text was updated successfully, but these errors were encountered:
Running npm install eslint@7 fixes things (fwiw). I'm guessing this is due to newer npm versions being better about complaining when there's conflicting peer dependencies?
When trying to
npm install
the dev environmentThe text was updated successfully, but these errors were encountered: