When I run `npm install`, it returns with `ERR! code EINTEGRITY` (npm 5.3.0)

Question

I am getting this error while running sudo npm install. On my server, npm was installed earlier. I've tried to delete the package-lock.json file, and ran npm cache clean --force, but it didn't work.

My npm version is 5.3.0.

The error:

npm ERR! code EINTEGRITY
npm ERR! sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA== integrity checksum failed when using sha512: wanted sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA== but got sha512-WXI95kpJrxw4Nnx8vVI90PuUhrQjnNgghBl5tn54rUNKZYbxv+4ACxUzPVpJEtWxKmeDwnQrzjc0C2bYmRJVKg==. (65117 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ubuntu/.npm/_logs/2017-11-29T05_33_52_182Z-debug.log

See Solution below to sidestep the cause of the problem, especially when connectivity is an issue. — SherylHohman
– SherylHohman, Commented Dec 21, 2017 at 10:12
Running following 2 commands solved my problem. $ rm -rf package-lock.json node_modules $ npm install — Kodali444
– Kodali444, Commented Mar 11, 2020 at 10:58

erikvold · Accepted Answer · 2021-07-18 22:56:59Z

399

See https://github.com/npm/npm/issues/16861

This worked for me:
npm cache verify

Then I re-ran:
npm install -g create-react-app

And it installed as expected: Issue resolved.

Other solutions mentioned in the GitHub issue include:

npm cache clean --force

OR

Deleting npm and npm-cache folders in Users%username%\AppData\Roaming (Windows 7 and Windows 10) and running npm install

OR

Update npm by via npm i -g npm

OR

Delete package-lock.json

OR

npm cache clean

OR

Do these steps to fix the problem:

Find all outdated packages and update theme:
npm outdated -g
sudo npm i -g outDatedPKG
Upgrade npm to latest version with:
sudo npm i -g npm
Delete package-lock.json file.
Delete _cacache directory in ~/.npm: npm cache verify
Every time I get that error, do steps 2 & 3.
If you still get the error, clear npm's cache:
npm cache clean --force

OR

Add proxy to .npmrc in ~ directory:

proxy=http://localhost:8123
https-proxy=http://localhost:8123

Try again! slow internet connection and censorship may cause this ugly problem.

OR

npm cache clear --force && npm install --no-shrinkwrap --update-binary

OR

npm config set package-lock false

edited Jul 18, 2021 at 22:56

erikvold

16.7k11 gold badges59 silver badges101 bronze badges

answered Dec 21, 2017 at 9:42

SherylHohman

18.2k18 gold badges94 silver badges101 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

jfajunior Over a year ago

Thank you! That was very helpful and I solved my problem choosing some of the given options.

SherylHohman Over a year ago

Super !! So Glad to Help :-)

Andres F. Over a year ago

Sheryl, first: thanks for taking the time to answer this. It's clear your answer was helpful to people. Can I ask you what each of these alternatives does, and why some may work when others don't? Thanks!

SherylHohman Over a year ago

@AndresF. I do not have a deep understanding of how the underbelly of yarn works, or when/why some methods work over others. In some cases they essentially accomplish the same thing, but go about triggering it in a different way. I linked to the github issue where all these solutions were presented - it is the source of the compiled list in my answer. I suggest research into the underbelly of yarn and npm, or checking out the github issue linked, perhaps reaching out to individual authors if necessary.

gnganapath Over a year ago

In case, any update in node js version in local machine, It will through this error.

|

Gaurav Joshi · Accepted Answer · 2018-02-15 12:02:40Z

86

Delete package-lock.json file and then try to install

answered Feb 15, 2018 at 12:02

Gaurav Joshi

1,0547 silver badges13 bronze badges

6 Comments

sathishpaul Over a year ago

Thanks for this comment, it helped me resolve the issue, when I was deploying a GatsbyJS site to Netlify.

Adam Bogdan Boczek Over a year ago

Tried all above and this was the solution!

Asanka Over a year ago

yeah It worked after deleting the package-lock.jason and re running npm install

Artem Over a year ago

Very bad solution. package-lock.json must be used to control all dependencies and versions

Gaurav Joshi Over a year ago

@Artem - EINTEGRITY issue happens when you have corrupt data in your package-lock json , in such scenario you have to delete the local copy of your package json and with help of git difference you can see a checksum mismatch so deleting is not the wrong solution you can always create a copy and see the version difference

|

sashoalm · Accepted Answer · 2022-01-25 06:22:39Z

51

The issue was indeed in package-lock.json, and after replacing it with a working version from another branch it worked.

What's interesting is seeing the diff:

So there really is some integrity checksum in the package-lock.json and it was replaced in our package-lock.json with a SHA1 instead of a SHA-512 checksum. See here for more info.

In case you don't have a working version in another branch. Consider the message

npm ERR! code EINTEGRITY
npm ERR!
  sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA==
integrity checksum failed when using sha512: wanted
  sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA==
but got
  sha512-WXI95kpJrxw4Nnx8vVI90PuUhrQjnNgghBl5tn54rUNKZYbxv+4ACxUzPVpJEtWxKmeDwnQrzjc0C2bYmRJVKg==
. (65117 bytes)

Find the package in package-lock.json using the first checksum:

sha512-MKiLiV+I1AA596t9w1sQJ8jkiSr5+ZKi0WKrYGUn6d1Fx+Ij4tIj+m2WMQSGczs5jZVxV339chE8iwk6F64wjA==

and put the third checksum into its "integrity" field:

sha512-WXI95kpJrxw4Nnx8vVI90PuUhrQjnNgghBl5tn54rUNKZYbxv+4ACxUzPVpJEtWxKmeDwnQrzjc0C2bYmRJVKg==

A more detailed description is here.

edited Jan 25, 2022 at 6:22

answered Mar 1, 2018 at 14:19

sashoalm

80.5k138 gold badges485 silver badges830 bronze badges

3 Comments

Mamen Over a year ago

where is package-lock.json file?

SherylHohman Over a year ago

@Mamen in the root directory of your app, next tp package.json. package.json lists the dependencies (packages) your app needs in order to compile/run. When you run yarn install or yarn, the packages listed in that file will be downloaded and installed, so the project/app can be run. The "lock" file is one difference between npm and yarn, ensuring package versions, and integrity.

x-yuri Over a year ago

The only solution that came close to solving it for me. Deleting package-lock.json should remedy it as well. At least in my case. Although that is apparently not desirable. And to be fair I must mention here that OP tried to delete the file, so the case that this answer addresses is probably somewhat different.

SANITH · Accepted Answer · 2017-12-01 05:24:50Z

38

Actually the above is related to the network connectivity in side the server. When I've good connectivity in the server, the npm install gone good and didn't throw any error

answered Dec 1, 2017 at 5:24

SANITH

3,3073 gold badges15 silver badges15 bronze badges

2 Comments

bmukorera Over a year ago

Mine worked after switching over to a vpn connection, so it's definitely a connection issue

D_Edet Over a year ago

Thanks. Seems its a network issue. Worked after I tried again.

Mercury · Accepted Answer · 2018-09-16 08:45:59Z

18

My problem was 2 things:

Bad package-lock.json file
The existance of npm-shrinkwrap.json together with the package-lock.json file

What i did is:

Deleted the package-lock.json file
Delete the npm-shrinkwrap.json file
Ran npm install again (which recreated a good package-lock file)

Fixed my error!

answered Sep 16, 2018 at 8:45

Mercury

8,0683 gold badges52 silver badges65 bronze badges

2 Comments

bertie Over a year ago

I had this problem building on AWS Codebuild. This worked for me. Thanks.

Felipe Belluco Over a year ago

In my case was the package-lock! Problem solved for me! Thanks!

Raj · Accepted Answer · 2018-11-16 19:36:55Z

13

I was stuck at this for a long time and this is what helped me.

Try this:

npm cache clean --force
npm install --update-binary --no-shrinkwrap

Found this answer after digging into GitHub issues!!

answered Nov 16, 2018 at 19:36

Raj

4,1498 gold badges33 silver badges55 bronze badges

Comments

eyllanesc · Accepted Answer · 2018-09-10 18:31:43Z

6

As a workaround, follow the below steps:

Go to the project directory
Remove the node_modules directory: rm -rf node_modules
Remove package-lock.json file: rm package-lock.json
Clear the cache: npm cache clean --force
Run npm install --verbose If after following the above steps still the issue exists then please provide us the output of installation command with --verbose.

edited Sep 10, 2018 at 18:31

eyllanesc

246k19 gold badges205 silver badges282 bronze badges

answered Sep 10, 2018 at 18:26

Vanessa Ortiz

691 silver badge2 bronze badges

1 Comment

Andi AR Over a year ago

I am new to npm. Verbose gave me some hint.

jfajunior · Accepted Answer · 2018-04-26 07:58:42Z

4

There are several valid and helpful responses here, but I would like to add that in my case the simplest solution was:

Delete package-lock.json;
Remove folder AppData\Local\npm\cache or AppData\Roaming\npm\cache;
Remove folder node_modules.staging;
Run npm install again.

After that everything ran smoothly.

answered Apr 26, 2018 at 7:58

jfajunior

1,2511 gold badge15 silver badges20 bronze badges

Comments

Sebastian D'Agostino · Accepted Answer · 2018-05-29 13:58:23Z

3

I had a very similar problem, and in my case it worked by doing:

npm clean

This is the nuclear option since it clears every package from the cache as expained here.

answered May 29, 2018 at 13:58

Sebastian D'Agostino

1,6752 gold badges29 silver badges45 bronze badges

Comments

Blackbam · Accepted Answer · 2018-08-09 15:17:11Z

3

Try the following:

npm cache clean --force

This has worked for me.

edited Aug 9, 2018 at 15:17

Blackbam

19.7k31 gold badges112 silver badges167 bronze badges

answered Aug 4, 2018 at 22:03

Kolaaa

2563 silver badges6 bronze badges

2 Comments

Blue Over a year ago

This does not add any value to the answers that are already here. The most highly up-voted comment already mentions npm cache clean --force, so this answer just reads as noise.

Donald Duck is with Ukraine Over a year ago

While this code may answer the question, providing additional context regarding how and/or why it solves the problem would improve the answer's long-term value.

Sai Ram · Accepted Answer · 2018-10-08 05:47:39Z

3

I was using private npm registry and trying to install private npm module. Logging to npm local registry fixed it (used command npm --add-user)

answered Oct 8, 2018 at 5:47

Sai Ram

4,4424 gold badges29 silver badges40 bronze badges

Comments

Matthew Blewitt · Accepted Answer · 2020-01-31 08:01:26Z

3

Updating .npmrc and the registry to https:// worked for me

registry=https://registry.npmjs.org/

answered Jan 31, 2020 at 8:01

Matthew Blewitt

4871 gold badge3 silver badges16 bronze badges

Comments

Aleks-Daniel Jakimenko-A. · Accepted Answer · 2020-09-11 08:40:18Z

3

This Worked for me . open the project in CMD the run

npm cache verify 
npm install 
npm start

edited Sep 11, 2020 at 8:40

Aleks-Daniel Jakimenko-A.

10.8k3 gold badges43 silver badges41 bronze badges

answered Sep 6, 2020 at 12:30

Insookwa

1091 silver badge5 bronze badges

Comments

SherylHohman · Accepted Answer · 2018-04-22 19:55:42Z

1

SherylHohman's answer solved the issue I had, but only after I switched my internet connection. Intitially, I was on the hard-line connection at work, and I switched to the WiFi connection at work, but that still didn't work.

As a last resort, I switched my WiFi to a pocket-WiFi, and running the following worked well:

npm cache verify

npm install -g create-react-app

create-react-app app-name

Hope this helps others.

edited Apr 22, 2018 at 19:55

SherylHohman

18.2k18 gold badges94 silver badges101 bronze badges

answered Feb 23, 2018 at 22:32

AJ Singh

314 bronze badges

Comments

user3966432 · Accepted Answer · 2018-09-07 07:22:40Z

1

I am behind my organization's proxy, running the following commands fixed the issue for me

npm config set proxy http://proxy.yourproxydomain.com:port
npm config set https-proxy http://proxy.yourproxydomain.com:port
npm config set strict-ssl false
npm config set registry https://registry.npmjs.org/

answered Sep 7, 2018 at 7:22

user3966432

4084 silver badges16 bronze badges

Comments

Chad Scira · Accepted Answer · 2020-02-25 13:30:24Z

1

This was not yet mentioned but make sure that your SYSTEM TIME is correct. If it is too out of sync it will cause a EINTEGRITY error. When you are doing npm publish / install.

answered Feb 25, 2020 at 13:30

Chad Scira

9,8893 gold badges59 silver badges51 bronze badges

Comments

Zach Pedigo · Accepted Answer · 2020-06-26 14:00:10Z

1

None of the above answers worked for me. The solution to my issue was to change the way the snapshot dependency was consumed inside the package.json. Use the following template to pull in the snapshot dependency that you need

"dependency": "git+http://github.com/[pathtoproject].git#[branchname]",

answered Jun 26, 2020 at 14:00

Zach Pedigo

4365 silver badges11 bronze badges

Comments

biggest_boy · Accepted Answer · 2020-10-30 18:27:58Z

1

I had the same issue. I used yarn instead of npm to install the dependencies and it worked.

yarn add *****

answered Oct 30, 2020 at 18:27

biggest_boy

4816 silver badges24 bronze badges

Comments

myxlptlk · Accepted Answer · 2020-12-02 08:33:10Z

1

After going through all the answers and executing most of them. Although I resisted to try the Restart magic, eventually, the issue is solved after restart on my macbook(MacOS Catalina Ver. 10.15.7).

It seems like a cache issue indeed but none of the commands that I have executed cleared the cache.

answered Dec 2, 2020 at 8:33

myxlptlk

1393 bronze badges

Comments

Kidus Yared · Accepted Answer · 2021-01-10 10:54:36Z

1

What worked for me was npm cache verify then re-run your command. All should be good.

answered Jan 10, 2021 at 10:54

Kidus Yared

214 bronze badges

Comments

dancl · Accepted Answer · 2021-01-20 21:48:33Z

1

In my case the sha command was missing from my linux distro; steps were

added the packages for sha512 (on my distro sudo apt install hashalot)
npm cache verify
rm -rf node_modules
npm install

answered Jan 20, 2021 at 21:48

dancl

7275 silver badges13 bronze badges

1 Comment

kuollam Over a year ago

In general, you just remove package-lock, folder node-modules and re-install again, this is the only solution that worked for me.

Ketcomp · Accepted Answer · 2018-02-13 16:35:57Z

0

Updating the .npmrc files' entries for scoped and un-scoped packages worked for me. So I ended up using the

npm config set @scope_name:registry SCOPED_REGISTRY_URL

and

npm config set registry PUBLIC_REGISTRY_URL

answered Feb 13, 2018 at 16:35

Ketcomp

4541 gold badge8 silver badges20 bronze badges

Comments

Güçlü Kıvanç · Accepted Answer · 2020-03-11 11:38:57Z

0

You should check Connection-specific DNS Suffix when type “ipconfig” or “ifconfig” in terminal

answered Mar 11, 2020 at 11:38

Güçlü Kıvanç

2362 silver badges5 bronze badges

Comments

code_Jammy · Accepted Answer · 2020-04-08 08:00:16Z

0

I faced same issue. Plus while I was trying to resolve from picking solutions from other devs, I faced few more issues like one listed here.

Angular 9 ng new myapp gives error The Schematic workflow failed

https://medium.com/@codewin/npm-warn-deprecated-request-2-88-2-b6da20766fd7

Finally after trying cache clean and verify and reinstall node of different versions and npm update, nvm and many other solution like set proxy and better internet connection, I still could not arrive to a resolve.

What worked for me is : I browsed a bit inside my C:\Users--- folder, I found package-lock.json and .npmrc files. I deleted those and reinstalled angular and tried. npm install and uninstall of different modules started working.

edited Apr 8, 2020 at 8:00

answered Apr 8, 2020 at 7:18

code_Jammy

171 silver badge8 bronze badges

Comments

Jaimil Patel · Accepted Answer · 2020-04-30 05:45:09Z

0

Before i was running this command

npm install typescript -g

after changing the command it worked perfectly.

npm install -g typescript

edited Apr 30, 2020 at 5:45

Jaimil Patel

1,3639 silver badges13 bronze badges

answered Apr 30, 2020 at 4:00

Bishwajit Vikram

1131 silver badge9 bronze badges

Comments

Mani Bharathy · Accepted Answer · 2020-05-15 06:12:07Z

0

I faced this issue. It was my network connectivity. I changed network (from Broadband WiFi to 4G WiFi) and tried. It worked.

My broadband ISP was blocking all http requests. That might be the reason I guess in my case.

answered May 15, 2020 at 6:12

Mani Bharathy

1171 gold badge3 silver badges13 bronze badges

Comments

k_a_ r_i_s- · Accepted Answer · 2020-05-25 17:28:33Z

0

all solutions failed for me till i checked router settings; it was set to only IPV4.. i changed and put ipv4v6 and all is working fine now.

answered May 25, 2020 at 17:28

k_a_ r_i_s-

237 bronze badges

Comments

Sinan Samet · Accepted Answer · 2021-02-26 10:14:54Z

0

Easy and fast fix for me was to npm install the specific package on which it said the sha is wrong. Say your package is called awesome-package.

My solution was:

npm i awesome-package

This updated my sha within the package-lock.json.

answered Feb 26, 2021 at 10:14

Sinan Samet

6,78213 gold badges57 silver badges97 bronze badges

Comments

Lakshmikanth Vallampati · Accepted Answer · 2021-06-01 06:59:34Z

0

If none of the above solved your problem, then just upgrade your npm verion and try. It worked for me.

answered Jun 1, 2021 at 6:59

Lakshmikanth Vallampati

12 bronze badges

1 Comment

blondelg Over a year ago

Welcome to SO, please consider to give mode detailed answers

rjhcnf · Accepted Answer · 2022-02-26 12:43:13Z

0

Updating nodejs version worked for me.

curl -fsSL https://deb.nodesource.com/setup_12.x | sudo -E bash - sudo apt-get install -y nodejs

answered Feb 26, 2022 at 12:43

rjhcnf

1,0771 gold badge9 silver badges15 bronze badges

Collectives™ on Stack Overflow

When I run `npm install`, it returns with `ERR! code EINTEGRITY` (npm 5.3.0)

35 Answers 35

9 Comments

6 Comments

3 Comments

2 Comments

2 Comments

Comments

1 Comment

Comments

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

35 Answers 35

9 Comments

6 Comments

3 Comments

2 Comments

2 Comments

Comments

1 Comment

Comments

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Related