-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Description
Hello,
First time running npm install
gave these warnings:
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
added 810 packages, and audited 811 packages in 56s
151 packages are looking for funding
run `npm fund` for details
30 vulnerabilities (21 moderate, 7 high, 2 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Then I ran npm audit fix --force
few times, and after that npm install
gave following error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @pmmmwh/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react-refresh
npm ERR! dev react-refresh@"^0.14.0" from the root project
npm ERR! peer react-refresh@"0.10.x || 0.11.x || 0.12.x || 0.13.x || 0.14.x" from [email protected]
npm ERR! node_modules/react-refresh-typescript
npm ERR! dev react-refresh-typescript@"^2.0.7" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react-refresh@"^0.8.1" from @pmmmwh/[email protected]
npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR! dev @pmmmwh/react-refresh-webpack-plugin@"^0.3.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react-refresh
npm ERR! peer react-refresh@"^0.8.1" from @pmmmwh/[email protected]
npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR! dev @pmmmwh/react-refresh-webpack-plugin@"^0.3.0" 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 file: ...
My question is 1) how do i approach to read this error logs 2) how to approach solving this 'dependency hell?' 3) Why did it throw error after updating some(many) packages?
Metadata
Metadata
Assignees
Labels
No labels