npm package seems to be corrupted

Question

I am getting these warnings and then errors at the end. What is the fix?

npm WARN deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
npm WARN tarball tarball data for @angular/compiler@^8.0.0 (sha512-ABZO4E7eeFA1QyJ2trDezxeQM5ZFa1dXw1Mpl/+1vuXDKNjJgNyWYwKp/NwRkLmrsuV0yv4UDCDe4kJOGbPKnw==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @angular/core@^8.0.0 (sha512-zeePkigi+hPh3rN7yoNENG/YUBUsIvUXdxx+AZq+QPaFeKEA2FBSrKn36ojHFrdJUjKzl0lPMEiGC2b6a6bo6g==) seems to be corrupted. Trying one more time.

isn't it possible that you have a cached version of it which is corrupted? try npm cache verify and then npm install/update — Patrik Alexits, Nov 22 '19 at 07:15
I did npm cache verify, npm update and npm install but getting same warnings. — Muzaffar Mahmood, Nov 22 '19 at 07:45
Remove angular globally and re-do an npm install -g @angular/cli — Jacopo Sciampi, Nov 22 '19 at 08:19
i am also getting the same error while creating new project in Ionic. Did npm cache clean, npm update, uninstall and install ionic, cordova. still same... Please let me know where these dependencies versions are listed. I mean the path of the json file where the npm is installing these component. Please help.. — Dip, Nov 26 '19 at 03:43

score 11 · Answer 1 · edited Jun 04 '20 at 13:01

11

Try removing package-lock.json and then npm install. This worked for me:

cd <your-project-directory>
rm package-lock.json
npm install

edited Jun 04 '20 at 13:01

Adrian Mole

49,934
160
51
83

answered Jun 04 '20 at 12:15

Parth Shah

167
1
7

score 4 · Answer 2 · answered Nov 07 '20 at 08:15

4

Remove package-lock.json
Remove node_modules,
and then install packages using npm install.

This resolved issue for me.

answered Nov 07 '20 at 08:15

Georges Feungap

456
3
8

score 1 · Answer 3 · answered Nov 27 '19 at 14:29

You need to disable your antivirus software and run cmd as an administrator. Don't forget disabling the windows firewall. As for the deprecated Core-js 2.6.10 I'm facing the exact same issue but at least it's a warning you can ignore. I've tried reinstalling Angular cli and manually updating Core-js to the latest version using npm install -g core-js@latest unfortunately neither worked. Also fsevents seems to be Mac related and nothing to worry about.

That seemd to by me case too. – yonexbat Jun 24 '20 at 15:05 — yonexbat, Jun 24 '20 at 15:05

score -1 · Answer 4 · answered Jul 03 '20 at 03:03

You need to confirm whether the Typescript is installed and after installing typescript it worked for me

running the below comment will show the typescript version

tsc -v

If it shows some error install the typescript

npm install -g typescript

If then typescript is installed you can try checking the Angular Cli version

ng --version

If it shows some error then install Angular Cli Ref: https://cli.angular.io/

npm install -g @angular/cli

Gerbrand Visscher · Answer 5 · 2022-06-01T13:55:00.510

-1

I had to reinstall node.js to fix this.

I had to uncheck the box for auto install chocolatey

edited Jun 01 '22 at 13:55

answered May 03 '22 at 12:43

Gerbrand Visscher

111
1
5

score -1 · Answer 6 · answered Oct 20 '22 at 19:38

-1

Changed the integrity to a relevant one, then it worked upon triggering the jenkins build. The hash updated was given in jenkins console logs.

answered Oct 20 '22 at 19:38

Manisha Sinha

1
2

Welcome to SO! Maybe there is a language barrier, but your answer is not clear. Can you elaborate more? – Marcelo Scofano Diniz Oct 25 '22 at 16:38

npm package seems to be corrupted

6 Answers6