Unable to resolve dependency tree error when installing npm packages

Question

When trying to install the npm packages using npm i command, I am getting the following exception:

I have tried reinstalling the Node.js package and setting the proxy to off using:

set HTTP_PROXY=
set HTTPS_PROXY=

The issue is still there. What I am doing wrong?

Update:

When I run the following command:

npm install --legacy-peer-deps

The following error is displayed:

Show your package.json - it looks like you've upgraded @angular/core, but did not upgrade @angular/http? — Adam, Oct 28 '20 at 18:41
my @angular/core version is 9.1.4, so shall i update @angular/http? — Pearl, Oct 29 '20 at 06:01
Please share your `package.json` file. The problem seems to be in your dependencies — Owen Kelvin, Nov 01 '20 at 08:52
Can you try to delete package-lock.json and node_modules and try to run npm update? Let me know if it work. — Fmerco, Nov 03 '20 at 10:08
Which version of npm are you using? If it is 7.0.4 you should update, because it has a bug: https://github.com/npm/cli/issues/2000 — adrisons, Nov 03 '20 at 10:08
The package-lock.json is not available. Yes, I have tried deleting node_modules with no luck. — Pearl, Nov 03 '20 at 10:14
is this still happening? Can you share the package.json file? — Supun Praneeth, Nov 04 '20 at 14:15
Has this been resolved? If so, and any of the answers were helpful to you, please mark one of them as "Accepted". Otherwise, if you'd like some more clarification, just say so. — Eliezer Berlin, Nov 06 '20 at 11:26
For me, As i had a backup, I deleted my local repo and made a fresh pull and then trying `npm install` again worked for me. — Huzaifa, Mar 05 '21 at 15:00

score 509 · Accepted Answer · edited Sep 05 '21 at 21:55

509

This is not related to an HTTP proxy.

You have dependency conflict (incorrect and potentially broken dependency) as it says, so try to run the command with --force, or --legacy-peer-deps. If it doesn't take effect, the temporary solution is using prior versions of the Node.js (downgrading the Node.js version) as it causes this kind of errors to happen sometimes.

Update based on the OP's update:

As you see, it fires the following error:

No matching version found for @angular/http@^9.1.4.

Take a look at angular/http page. Note that the latest version for that deprecated package is 7.2.16 while you request an upper version (e.g., ^9.1.4)! So, try to check the project dependencies and follow the raised errors in order to solve the problem.

edited Sep 05 '21 at 21:55

Peter Mortensen

30,030
21
100
124

answered Oct 30 '20 at 20:48

Amirhossein Mehrvarzi

15,028
7
42
69

@Pearl please show the output result of `--force` and `--legacy-peer-deps` commands – Amirhossein Mehrvarzi Nov 02 '20 at 10:31
91

Thanks `npm install --legacy-peer-deps` works for me – Gaurav Patil Apr 13 '21 at 05:15
will that flag install only peer deps? – Aashiq May 26 '21 at 11:50
6

@Aashiqahmed It tells NPM to *ignore* peer deps and proceed with the installation anyway – Amirhossein Mehrvarzi May 26 '21 at 12:25
,react folder in project > Open in Integrated Terminal I had this following error $ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree Below command worked. thanks npm install --legacy-peer-deps – Devaski Aug 23 '21 at 19:00
1

Thanks, downgrade node version from 15 to 14 worked for me. – asmaa Mar 08 '22 at 12:41
`npm install --force` worked for me – PVIJAY Mar 24 '22 at 03:03
As it turns out, some packages manage to break peer dependencies on all their own, they don't even need to depend on the project being worked on to break. Happens a lot with packages made for legacy versions of Angular and React. – Tiramonium May 05 '22 at 16:33

score 232 · Answer 2 · answered Dec 17 '20 at 21:10

232

Try this command-

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

answered Dec 17 '20 at 21:10

Ali Hasan

2,531
1
4
7

105

please explain what it does – Gerfried Apr 14 '21 at 13:10
15

@Gerfried, It tells NPM to ignore peer deps and proceed with the installation anyway. – Aashiq May 27 '21 at 07:05
1

If using npm 5 or greater no need --save flag as it automatically saves dependencies – Naga Feb 11 '22 at 10:06

score 101 · Answer 3 · answered Jan 15 '21 at 09:18

101

In addition to using the --legacy-peer-deps command line option, this can also be set more permanently as a config option:

npm config set legacy-peer-deps true

answered Jan 15 '21 at 09:18

friederbluemle

28,615
14
96
99

4

The best option if `npm install` is run indirectly, e.g. by a script. – kszl Jun 24 '21 at 19:57
2

what does this do – Sam Aug 10 '21 at 23:36
@Arefe, Aashiq explained in another, similar answer, that this command (legacy-peer-deps) "tells NPM to ignore peer deps and proceed with the installation anyway" – Alvaro Rodriguez Scelza Nov 16 '21 at 21:08
npm config set legacy-peer-deps true This command is working for me, Thanks – Krishan Gopal Apr 22 '22 at 09:34

makkasi · Answer 4 · 2021-09-10T11:16:01.237

First to understand the problem. Here is what I have as error:

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: project-admin@11.0.0
npm ERR! Found: @angular/common@11.0.3
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"11.0.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR! node_modules/@agm/core
npm ERR!   @agm/core@"3.0.0-beta.0" from the root project

First you should start to read the problem from the bottom to the top. Here @agm/core@3.0.0-beta.0 requires angular common 9.1.0 or 10.0.0. And the top message says that the angular common found is actually 11.0.3.

(If you want to understand dependencies little bit better, here is very simple site: How npm3 Works)

dependencies — these are the essential dependencies that you rely on and call in your project’s code
devDependencies — these are your development dependencies, for example, a prettier library for formatting code
peerDependencies — if you set a peer dependency in your package.json, you are telling the person who installs your package that they need that dependency with the specified version
optionalDependencies — these dependencies are optional and failing to install them will not break the installation process
bundledDependencies — it’s an array of packages that will come bundled with your package. This is useful when some 3rd party library is not on NPM, or you want to include some of your projects as modules

So what should be the solution then? The problem is about peer dependencies. The solution is to downgrade angular common or the solution is to use legacy dependencies logic for installing packages using --legacy-peer-deps. So --legacy-peer-deps does not try to install the peerDependencies automatically. Is this going to work for you? Probably, yes. But you should add specific instructions how to do that, or to make the use of --legacy-peer-deps automatic for future installation of the project packages with this code from one of the previous answers:

npm config set legacy-peer-deps true

In my case I installed the package and I tried to run ng serve, but because --legacy-peer-deps was used, there were dependency packages which were not installed. I had to install those manually (because I did not set the configuration from the code above). At the end installing about five packages manually, all with --legacy-peer-deps, I ended to a package that could not be installed and I did not try to continue, because my project was throwing warnings like crazy and there were a lot of packages for audit too. So my decision was not to use this package and to find an alternative.

Other solutions that I read about along the way:

downgrade Node.js to v14. This will downgrade npm. It might not be v14, but this was the version that was most widely downgraded to.
Some people use Yarn to force package installation - personally I don't understand how this works, because I haven't used Yarn.
downgrading Angular and the global Angular CLI version to version that will satisfy the requirement. In my case it is angular/common, and in the question it's angular/core, but both require downgrading the whole angular right (I am not sure about this here).
the package you install might have a higher version that doesn't require downgrading Angular. You might try to use the https://updatepackagejson.com/ to upgrade your packages to the latest, but this is in case your project is quite new.

That's the best answer because it is the only answer which explained the error log from OP instead of stupidly applying force or legacy-peer-deps option. Better to stick to npm 6 than pushing npm 7 and force/legacy-peer-deps on it to avoid fixing your dependencies issues — HoLengZai, Apr 12 '22 at 07:52
By far the best answer, others just fix the issue, but not caring about the underlying problem nor give insightful suggestions on why the issue is occurring. — jeffng50, May 18 '22 at 09:27

Trott · Answer 5 · 2021-08-22T17:28:23.707

When using npm 7, this comes up a lot because peer dependencies issues are treated as errors in version 7 whereas they were generally only warnings in version 6. Usually using --legacy-peer-deps makes it work with npm 7.

When that doesn't work, an option is to downgrade to npm 6. Downgrading Node.js is not necessary (but not harmful either). The relevant dependency management code is in npm. Downgrading Node.js will often work coincidentally because doing so will often downgrade npm as well.

Another option that is less disruptive than downgrading npm is using npx to use the previous version of npm for just the install command: npx -p npm@6 npm install

And when all else fails, it's often worth a shot to remove the node_modules directory and package-lock.json, and then run npm install again. That regenerates node_modules and package-lock.json.

@alentejo by removing the npm folder in theC:\Users\{your name}\AppData\Roaming , npm cache clear --force and then npm install -g npm@ — Valdemar Vreeman, May 20 '21 at 08:09

Vinay Somawat · Answer 6 · 2022-05-16T08:37:32.387

51

Finally, I found the answer. Try this command -

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

Described here legacy-peer-deps

edited May 16 '22 at 08:37

answered Dec 08 '21 at 09:18

Vinay Somawat

1,029
11
19

10

An explanation would improve this answer – derekbaker783 Mar 03 '22 at 16:44
1

Edit the answer with an explanation. – Vinay Somawat May 16 '22 at 08:38

ztom · Answer 7 · 2021-02-08T11:03:44.910

This happens for some packages after updating to npm 7.

Paramter --legacy-peer-deps can help:

npm i --legacy-peer-deps

Described here legacy-peer-deps

Causes npm to completely ignore peerDependencies when building a package tree, as in npm versions 3 through 6.

If a package cannot be installed because of overly strict peerDependencies that collide, it provides a way to move forward resolving the situation.
...

You can set this option to true by default (not recommended by npm):

npm config set legacy-peer-deps true

Or just wait until these packages get up to date.

score 15 · Answer 8 · answered Apr 07 '22 at 17:23

15

Just Do 2 simple steps:

First, execute this in your terminal.

npm config set legacy-peer-deps true

Second, Clear cache

npm cache clean --force

And finally, execute your command this will work for sure.

answered Apr 07 '22 at 17:23

Vinit Dabhi

231
3
4

Does clearing cache help here? Do we really need Step 2? – Hari Reddy Apr 29 '22 at 04:01

score 13 · Answer 9 · edited Sep 05 '21 at 22:41

13

The problem is related to a dependency conflict or broken dependency. You can proceed by accepting the incorrection of dependency by forcing an install.

Solution: Using command with --force.

Your command will be like npm install --force @your-npm-package.

Note: You can use yarn to install a dependency if it's available in to install with the yarn package manager.

edited Sep 05 '21 at 22:41

Peter Mortensen

30,030
21
100
124

answered Aug 04 '21 at 17:19

Aly

2,648
2
11
19

score 10 · Answer 10 · answered Nov 05 '20 at 17:53

10

Try removing the node modules and package-lock.json file and run command npm install or Try npm cache clean --force

answered Nov 05 '20 at 17:53

Kavinda Senarathne

1,435
9
14

score 10 · Answer 11 · edited Sep 05 '21 at 22:34

10

First I tried

npm install

It gave me error unable to resolve dependency tree and based on the help information from this command,

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.

I tried this command:

npm install --legacy-peer-deps

And it solved my problem.

edited Sep 05 '21 at 22:34

Peter Mortensen

30,030
21
100
124

answered May 20 '21 at 01:07

Qin Chenfeng

331
4
5

score 8 · Answer 12 · edited Sep 05 '21 at 22:30

The fastest solution: npm install --legacy-peer-deps

Explanation:

In npm versions 3 through 6, peerDependencies were not automatically installed, and would raise a warning if an invalid version of the peer dependency was found in the tree. As of npm v7, peerDependencies are installed by default.

npm docs: peerDependencies

Your dependency contains some peerDependencies that conflict with the root project's dependency.

As it described in the npm ERR log.

Rigers Leka · Answer 13 · 2021-11-24T16:24:35.683

NPM can be used to install and manage versions of dependencies in your projects.

I had it the same issue on React versions in relation with npm version

npm error found types/react@16.14.20

So it might be package-versions that need to be installed based on your package.json

It gives errors in npm@7 version and cannot install node modules. If you will downgrade npm version to 6, those problems will become warnings and the problem will be resolved.

Try to prove this command: npm install -g npm@6
Check if version is already installed: npm --version
Remove and install node_modules package:

a) Remove rm -rf node_modules

b) Install: npm i

Eliezer Berlin · Answer 14 · 2020-11-06T11:25:40.207

The problem seems to be that gf-kautomata-pipeline-ui is using Angular 9, while @angular/http requires Angular 7. (@angular/http was deprecated and eventually removed, and all its functionality was moved into @angular/common instead.)

See: https://www.npmjs.com/package/@angular/http

If you're running Angular 9, then

delete @angular/http from your package.json (You don't need it in Angular 9)
Make sure you have @angular/common in your package.json.
Run npm i.

If you're running Angular 7, then open up your package.json and check to make sure all of your Angular packages are no higher than ^7.0.0. You may also need remove gf-kautomata-pipeline-ui, or contact the author of gf-kautomata-pipeline-ui and find out if the library is compatible with Angular 7.

@Pearl I see in the comments you wrote that your @angular/core is Angular 9, not Angular 7. Are you half-way through an upgrade from 7 to 9? — Eliezer Berlin, Nov 05 '20 at 11:56

score 4 · Answer 15 · answered Nov 26 '21 at 09:04

4

Try 2 options to resolve this issue option1 => delete node_modules and package_lock.json after run
npm cache clean --force after npm i --force option 2 => run npm install --save --legacy-peer-deps

answered Nov 26 '21 at 09:04

aakash sharma

79
2

score 3 · Answer 16 · answered Feb 21 '22 at 21:11

3

this works for me npm install --save --legacy-peer-deps

answered Feb 21 '22 at 21:11

Fahad

51
1

score 2 · Answer 17 · edited Sep 05 '21 at 22:28

In my case, I started getting the error (below) after upgrading npm from version 6 to 7.

npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree

...

npm ERR! Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.

In my case compiling with either --legacy-peer-deps or --force flags resulted in a useless bundle.

So I tried deleting the node_modules, package-lock.json, and bundle using yarn install. This generated a yarn.lock file and created package-lock.json that worked fine in subsequent npm runs.

P.S.: I am using the temporary workaround until npm 7 works fine with my project: after that, I will delete yarn.lock, package-lock.json and folder node_modules, and recompile with npm

rm -rf node_modules
rm package-lock.json
yarn install
# Generates a yarn.lock file and a new package-lock.json

# Continue with npm
npm start

score 1 · Answer 18 · edited Sep 05 '21 at 22:25

1

I just update my Node.js and it works for me:

node -v

Output:

V xxxx

And:

sudo npm install -g n

(Use this command to install the stable node release.)

sudo n stable

edited Sep 05 '21 at 22:25

Peter Mortensen

30,030
21
100
124

answered Apr 05 '21 at 16:03

Farbod Aprin

716
1
6
16

score 1 · Answer 19 · edited Sep 05 '21 at 22:29

1

If you have node_modules folder and package-lock.json file in your root directory then remove those:
```
rm -r node_modules
rm package-lock.json
```

Then run commands:

npm install --save --legacy-peer-deps
npm audit fix --force

Create .env file in the root directory and paste below code:
```
SKIP_PREFLIGHT_CHECK=true
```
Now, start your project:
```
npm start
```

edited Sep 05 '21 at 22:29

Peter Mortensen

30,030
21
100
124

answered Apr 12 '21 at 06:28

Prithu Shahi

21
4

score 1 · Answer 20 · edited Sep 05 '21 at 22:39

1

I have faced this issue many times. At last I found a solution:

npm install react-native-paper  --legacy-peer-deps

edited Sep 05 '21 at 22:39

Peter Mortensen

30,030
21
100
124

answered Jun 21 '21 at 15:20

Mazhar k

131
1
6

score 1 · Answer 21 · answered Jan 25 '22 at 06:03

1

This is an issue of node version Some latest versions of the node could show errors like these.

https://github.com/nvm-sh/nvm I use NVM to manage Node versions on the system and use node 12 to get past this error

command to change version

nvm use 12

answered Jan 25 '22 at 06:03

samridhgupta

1,539
1
16
31

score 1 · Answer 22 · answered Apr 18 '22 at 15:48

1

npm install --legacy-peer-deps

This worked for me

answered Apr 18 '22 at 15:48

komal dubey

31
3

score 0 · Answer 23 · answered May 08 '21 at 16:46

Resetting package-lock.json works good for me all the time:

git checkout -- package-lock.json

Details: Been experiencing this a lot when updating all packages of the legacy project - I highly don't recommend using npm audit fix nor npm i --force. Deleting the package-lock.json didn't work for me all the time as well. Rollback to the working version of package.json + package-lock.json and add packages turned out to be the safest and fastest variant for me.

score 0 · Answer 24 · edited Sep 05 '21 at 22:36

0

In my case I was having trouble with a @babel/core dependency, but I didn't want to use --force, because I was not sure about the consequences, so I went to https://www.npmjs.com/, looked for the package and replaced my old version with the newest one. That did the work.

edited Sep 05 '21 at 22:36

Peter Mortensen

30,030
21
100
124

answered May 23 '21 at 16:37

AlbertSawZ

19
3

score 0 · Answer 25 · edited Sep 05 '21 at 22:37

0

I solved this with by lowering the version of Node.js from the last version to the LTS version.

edited Sep 05 '21 at 22:37

Peter Mortensen

30,030
21
100
124

answered Jun 01 '21 at 08:46

Dor Levi

85
1
3

I was running into this issue on an LTS version of Node. – derekbaker783 Mar 03 '22 at 16:46

score 0 · Answer 26 · answered Jun 13 '21 at 14:46

Just in case, I did have similar behavior, when I tried either npm upgrade my current Angular 11.x based boilerplate from previous ng new or create new ng new abc based on Angular 12.x. I simply forgot to upgrade Angular CLI. So this npm install -g @angular/cli@latest solved my errors during ng new abc.

score 0 · Answer 27 · answered Jun 17 '21 at 06:17

For those who are getting errors while installing Bootstrap Paginator or table next

npm install react-bootstrap-table2-paginator --save

or

npm install react-bootstrap-table-next --save

Solution: Add --legacy-peer-deps after the command like

npm install react-bootstrap-table2-paginator --save --legacy-peer-deps
npm install react-bootstrap-table-next --save --legacy-peer-deps

score 0 · Answer 28 · answered Jul 12 '21 at 15:18

Even after uninstall/install NPM and CLI if still does not work then make sure you are inside the project folder. For example, you have created a root folder "myapplication". Now, you are running CLI command to create a brand new application under myapplication folder. After running command, you would get error like "ERESOLVE unable to resolve dependency tree". So, instead of running command on myapplication folder, go to new application folder inside myapplication folder and run/execute angular application. It would work fine.

score 0 · Answer 29 · edited Sep 05 '21 at 22:42

0

Yarn has a feature for solving this. If you can, try to use it for installing the package.

edited Sep 05 '21 at 22:42

Peter Mortensen

30,030
21
100
124

answered Aug 30 '21 at 03:28

Estiventh Leonardo Neira Aldan

374
3
4

3

Can you please state which feature? – MilosMarkoni Dec 03 '21 at 10:10

Khadim H. · Answer 30 · 2022-01-07T10:08:26.080

0

ERESOLVE unable to resolve dependency tree error then add in the last of any dependency installation --legacy-peer-deps

Like: I am installing the socket.io so, I add --legacy-peer-deps in the last

$ npm install @nestjs/platform-socket.io @types/socket.io --legacy-peer-deps

edited Jan 07 '22 at 10:08

answered Dec 27 '21 at 07:48

Khadim H.

339
1
7

score 0 · Answer 31 · answered Apr 27 '22 at 10:57

0

https://i.stack.imgur.com/6uz7m.png npm install --save --legacy-peer-deps

answered Apr 27 '22 at 10:57

Vipin Chauhan

36
2

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - [From Review](/review/late-answers/31635922) – SecretAgentMan May 02 '22 at 18:33

Julio Cachay · Answer 32 · 2022-04-27T22:36:20.073

For this case: I was having this issue: ERESOLVE unable to resolve dependency tree in an angular 13 project that used some packages from a private npm feed in azure devops.

To access this repository, I created an .npmrc file. Because of this, the npm install command would search all packages in my private repository and not in npm feed anymore. The unable to resolve the dependency tree error happened because the npm install command could not find many of the packages that were hosted in the npm feed and not my private feed.

I found this amazing answer on how to scope packages

Based on this I made some changes:

In my library Package.json, update the name to have a scope name @mylib

"name": "@myLib/command-queue",

Build and publish this package to my private feed
In my client app (the one that uses this package), update the .npmrc file to use my private feed for packages in this scope only

@myLib:registry=https://pkgs.dev.azure.com/...
always-auth=true

Now, whenever I run the command npm install, if the package has the scope @myLib, it will look for it in my private feed, and use the npm feed for all other cases (i.e. @angular/...)

This is an example of my client app Package.json

    "@angular/platform-browser-dynamic": "~13.3.0",
    "@angular/router": "~13.3.0",        <-- this comes from npm
    "@myLib/jcg-command-queue": "^2.2.0", <-- This comes from my private feed

Also, with this change, there is no need to add --legacy-peer-deps to the npm install command anymore.

score -1 · Answer 33 · answered Mar 02 '21 at 22:29

-1

npm audit fix --force

Worked for me

answered Mar 02 '21 at 22:29

Relu Mesaros

4,648
3
23
33

2

While this code block may answer the question, it would be best if you could provide a little explanation for why it does so. – nik7 Apr 21 '21 at 17:53

score -1 · Answer 34 · answered Mar 31 '21 at 11:08

-1

Just Do Simple thing:

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

answered Mar 31 '21 at 11:08

yash sanghavi

337
2
5

3

While this code block may answer the question, it would be best if you could provide a little explanation for why it does so. – nik7 Apr 21 '21 at 17:53

score -1 · Answer 35 · edited Sep 05 '21 at 22:27

-1

Here is the solution.

Go to the project directory and do:

sudo rm ./package-lock.json
sudo npm install --force

edited Sep 05 '21 at 22:27

Peter Mortensen

30,030
21
100
124

answered Apr 06 '21 at 07:58

SIDDHANT JOHARI

72
5

score -1 · Answer 36 · edited Sep 05 '21 at 22:32

-1

None of the previous answers helped me.

For me, updating npm to the latest version (to 7.11.1 from 7.8) using npm i -g npm fixed the issue for me.

edited Sep 05 '21 at 22:32

Peter Mortensen

30,030
21
100
124

answered Apr 26 '21 at 20:07

Eliav Louski

1,877
1
15
30

score -2 · Answer 37 · edited Sep 05 '21 at 22:23

-2

I finally found a solution:

install nvm
use nvm to install Node.js
enter cmd to use the LTS version
after that, my installation worked. It should be working for you too.

edited Sep 05 '21 at 22:23

Peter Mortensen

30,030
21
100
124

answered Feb 13 '21 at 15:16

kode

61
1
1

score -2 · Answer 38 · edited Sep 05 '21 at 22:31

-2

Add the dependency in file package.json
Do npm install

Still seeing the error? Then

npm install --force`

edited Sep 05 '21 at 22:31

Peter Mortensen

30,030
21
100
124

answered Apr 21 '21 at 22:08

Raj Raj

1
1

score -2 · Answer 39 · edited Sep 05 '21 at 22:33

-2

I had the same issue

npm install --legacy-peer-deps

This works for mine too. But I have a simpler answer. Just change the version number of it in the package.json file that is required. Then use

npm i

This will solve your problem (generate a new project as usual, without any potentially broken dependency issue).

edited Sep 05 '21 at 22:33

Peter Mortensen

30,030
21
100
124

answered May 07 '21 at 19:12

shalitha anuradha

53
6

score -4 · Answer 40 · edited Sep 05 '21 at 22:37

-4

Start with the npm i --legacy-peer-deps flag first, and then use the --force flag next.

edited Sep 05 '21 at 22:37

Peter Mortensen

30,030
21
100
124

answered Jun 13 '21 at 06:44

pius

19
1

Unable to resolve dependency tree error when installing npm packages

40 Answers40

Linked

Related