CODEWITHSUNDEEP
npmhillavaadin-fusion
yeferson cordoba
yeferson cordoba

Reputation: 71

I am not able to install npm packages on my vaadin project

happy new year!

Any package that I am trying to install I am getting this:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @rollup/[email protected]
npm ERR! Found: dev @rollup/plugin-typescript@"^3.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev @rollup/plugin-typescript@"^3.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 ~/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     ~/.npm/_logs/2022-01-02T16_54_42_026Z-debug.log

I am trying to use this npm install --save @fortawesome/fontawesome-free

I don't understand what could be wrong.

Upvotes: 1

Views: 1049

Answers (4)

dorianDevTech
dorianDevTech

Reputation: 114

Did you try this :

sudo npm install --save @fortawesome/fontawesome-free

Upvotes: 0

The Fabio
The Fabio

Reputation: 6250

I will guess you have decided to update npm itself recently on your local env.

if you run the following (as per your error message), it should install dependencies without trouble.

npm i --legacy-peer-deps

Running npm v8+ to update your dependencies will upgrade the version of your package-lock.json. The issue is that your repo libraries have many old dependencies which might not be compatible with this update. When you run npm with --legacy-peer-deps it uses the old ways...

Upvotes: 1

90linux
90linux

Reputation: 194

I have encountered similar problems. After checking, I found that the primary group permission of the node program home directory is 500.500, which needs to be set to root root

Upvotes: 0

Rom Kadria
Rom Kadria

Reputation: 61

as it said in the error, you are handling an old package dependency and therefore you can use --force, or --legacy-peer-deps

Another solution that worked for me, and I think is better, try to install it through pnpm, as it seems to handle it.

Upvotes: 1

Related Questions