[NPM error] - NPM err code eresolve and NPM err eresolve could not resolve problems

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/webpack
npm ERR! peer [email protected]“^4.0.0 || ^5.0.0” from @soda/[email protected]
npm ERR! node_modules/@soda/friendly-errors-webpack-plugin
npm ERR! @soda/[email protected]“^1.8.0” from @vue/[email protected]
npm ERR! node_modules/@vue/cli-service
npm ERR! peer @vue/[email protected]“^3.0.0 || ^4.0.0 || ^5.0.0-0” from @vue/[email protected]
npm ERR! node_modules/@vue/cli-plugin-babel
npm ERR! dev @vue/[email protected]“~5.0.0” from the root project
npm ERR! 4 more (@vue/cli-plugin-eslint, @vue/cli-plugin-router, …)
npm ERR! [email protected]“^5.54.0” from @vue/[email protected]
npm ERR! node_modules/@vue/cli-plugin-babel
npm ERR! dev @vue/[email protected]“~5.0.0” from the root project
npm ERR! 17 more (@vue/cli-plugin-eslint, @vue/cli-service, …)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! [email protected]“5.0.0” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/webpack
npm ERR! peer [email protected]“^2.0.0 || ^3.0.0 || ^4.0.0” from [email protected]
npm ERR! node_modules/less-loader
npm ERR! [email protected]“5.0.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! See C:UsersadminAppDataLocal pm-cacheeresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersadminAppDataLocal pm-cache_logs?2-05-07T09_45_32_750Z-debug-0.log

Here is a small series npm i less [email protected] -D Or the above error occurs in other dependent packages

May be npm Version error report

resolvent ： Add after command

–legacy-peer-deps

–legacy-peer-deps The role of

stay NPM v7 in , Now installed by default peerDependencies.

In many cases , This can lead to version conflicts , This interrupts the installation process .

–legacy-peer-deps The sign is in v7 Introduced in , The purpose is to bypass peerDependency Automatic installation ; It tells NPM Ignore the various... Introduced in the project modules The same between modules But different versions have problems and continue to install , Ensure that different versions of each introduced dependency are used for itself modules coexistence .