修复安装 NPM 包的上游依赖冲突

Question

I am trying to npm install vue-mapbox mapbox-gl, and I'm getting a dependency tree error.

I'm running Nuxt.js SSR with Vuetify and haven't installed anything related to Mapbox prior to running this install and am getting this error.

38 error code ERESOLVE
39 error ERESOLVE unable to resolve dependency tree
40 error
41 error While resolving: [1mexample[22m@[1m1.0.0[22m
41 error Found: [1mmapbox-gl[22m@[1m1.13.0[22m[2m[22m
41 error [2mnode_modules/mapbox-gl[22m
41 error   [1mmapbox-gl[22m@"[1m^1.13.0[22m" from the root project
41 error
41 error Could not resolve dependency:
41 error [35mpeer[39m [1mmapbox-gl[22m@"[1m^0.53.0[22m" from [1mvue-mapbox[22m@[1m0.4.1[22m[2m[22m
41 error [2mnode_modules/vue-mapbox[22m
41 error   [1mvue-mapbox[22m@"[1m*[22m" from the root project
41 error
41 error Fix the upstream dependency conflict, or retry
41 error this command with --force, or --legacy-peer-deps
41 error to accept an incorrect (and potentially broken) dependency resolution.
41 error
41 error See /Users/user/.npm/eresolve-report.txt for a full report.
42 verbose exit 1

What's the right way to go about fixing this upstream dependency conflict?

Answer 1

Looks like it's a problem with Peer Dependencies in the latest version of npm (v7) which is still a beta version. try with npm install --legacy-peer-deps for detail info check this https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major

Answer 2

Use --legacy-peer-deps after npm install . For example, if you want to install radium, use:

npm install --legacy-peer-deps --save radium

Answer 3

There are TWO ways:

1. use npm install --legacy-peer-deps to install, and if this doesn't work use

2. force method. add --force next to npm install: npm install --force

Answer 4

直到 npm 版本 7.19.1 仍然存在相同的问题，升级到版本 7.20.3后使用命令npm install -g npm@latest和npm audit fix所有 pkg​​s 修复没有错误。

Answer 5

You can follow this command

first type:

npm config set legacy-peer-deps true

then type:

npx create-react-app my-app

Answer 6

To Solve Fix the upstream dependency conflict installing NPM packages Error

Method 1. Just Use --legacy-peer-deps after npm install.

For example, if you want to install axios, use

npm install --legacy-peer-deps --save axios.

Method 2. Updating npm and audit fix

npm I -g npm@latest
npm audit fix --force

Method 3. using --force to install packages

npm install axios --force

Answer 7

I tried multiple ways but nothing was working for me. At last tried this and it worked npm config set legacy-peer-deps true Run this in the project folder and then try to install any package. Might work for you as well

Answer 8

要解决 npm 依赖项和与 npm 包的冲突，请使用 npm-check-updates https://www.npmjs.com/package/npm-check-updates

Answer 9

• delete the package-lock.json file
• modify the package.json , updating the version as indicated by the peer dependancy
• run npm install or npm udpate

Answer 10

What is happening is that your dependency mexample requires mmapbox-gl v1.13.0 and mvue-mapbox requires v0.53.0.

NPM don't really know what to do, so it gives a warning. You can bypass the errors using -- force or --legacy-peer-deps but you are ignoring an error.

Production Options:

1. Probably one of your packages is outdated. Upgrading packages and fixing upgrade errors might fix the dependency conflict.

2. Overriding a dependency manually to avoid the warning and error. What you are doing is setting the version to a specific one that you know that works. Usually the newer version.

Example solution with override. Your package.json will look like that:

{
  "name": "my-app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "mexample": "^1.2.0",
    "vue-mapbox": "*"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "overrides": {
    "mmapbox-gl": "1.13.0"
  }
}

The last option is bypassing using either:

1. --legacy-peer-deps Ignores completely all peerDependencies using the newest version without pinning on package-lock.json
2. --force Forces the use of the newest pinning all the versions on package-lock.json

Extra: You shouldn't use "*" as a version because might update major and break dependencies.

Answer 11

使用 npm install --legacy-peer-deps

Answer 12

我已将我的节点版本降级为10.23.1 ，它运行良好。

Answer 13

A lot of upvotes for using --legacy-peer-deps but if --force works I would recommend using that since it still pins many dependency versions while --legacy-peer-deps ignore peer dependencies entirely. See example below:

https://stackoverflow.com/a/66608842/3850405

Started getting this error on Azure DevOps a few days ago. Initially thought it was a glitch on Azure side but since it continued we started looking into it a bit more.

Turns out the agent we are using, windows-2022 , was updated a few days ago.

https://github.com/actions/virtual-environments/commit/2950cbfeab88a6a6202fa31d7371e574dbe2dc51

Node and NPM now match the Latest Node.js LTS Version: 16.15.1 (includes npm 8.11.0)

https://nodejs.org/en/download/

You can view all agents included Software here:

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software

After reading on Microsoft Visual Studio Developer Community they recommend downgrading Node.js using Node.js Tool Installer task like this:

- task: NodeTool@0
  inputs:
    versionSpec: '16.14.2' 

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/node-js?view=azure-devops

https://developercommunity.visualstudio.com/t/npm-install-fails-in-azure-devops-hosted-agent/1606509

However we decided that we do not want to downgrade Node.js so first step was matching Node.js locally with LTS Version: 16.15.1 and npm 8.11.0.

When running npm ci we then got the same error locally.

Tried npm ci --force and we then got this error:

npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.

npm install gave the same error even after node_modules was manually removed but npm install --force worked and it generated a new package-lock.json .

npm ci still failed with the same error but running npm ci --force worked. We decided to update Azure DevOps .yml to include --force and checked in the new package-lock.json . After doing this everything works like before and we can now update our packages one by one.

Answer 14

I resolved this by adding

 steps: - task: NodeTool@0 inputs: versionSpec: '12.x'

Answer 15

I was stuck on this issue for long which also makes error from other commands which calls for some install commands that was breaking.

The only solution that works (maybe suppresses the error) is

npm config set legacy-peer-deps true

This will set the configuration of legacy-peer-deps to true

Answer 16

this works for sure

npm config set legacy-peer-deps true

run it then install anything with npm