Closed
Description
Modern npm gives you when npm install in that repo:
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/typescript
npm ERR! dev typescript@"^4.6.3" from the root project
npm ERR! peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from [email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin/node_modules/tsutils
npm ERR! tsutils@"^3.21.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@"^5.17.0" from the root project
npm ERR! 3 more (tsutils, tsutils, ts-node)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^3.0.0" from [email protected]
npm ERR! node_modules/gulp-tsb
npm ERR! dev gulp-tsb@"^4.0.6" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR! peer typescript@"^3.0.0" from [email protected]
npm ERR! node_modules/gulp-tsb
npm ERR! dev gulp-tsb@"^4.0.6" 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!
npm ERR! For a full report see:
npm ERR! C:\Users\Segev\AppData\Local\npm-cache\_logs\2023-02-23T09_15_34_071Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Segev\AppData\Local\npm-cache\_logs\2023-02-23T09_15_34_071Z-debug-0.log
It makes sense to me that this is something that should be fixed. For now, I'm using --legacy-peer-deps.