Incorrect integrity when fetching from the cache

Yarnpkg Problem Overview

When running yarn add --dev jest, I got error Incorrect integrity when fetching from the cache.

Full output:

tests (master)$ yarn add --dev jest
yarn add v1.19.0
info No lockfile found.
[1/4] Resolving packages...
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > left-pad@1.3.0: use String.prototype.padStart()
[2/4] Fetching packages...
error Incorrect integrity when fetching from the cache
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

I tried removed node_modules, re-ran yarn install and yarn add --dev jest to no avail.

How do I fix this?

Yarnpkg Solutions

Solution 1 - Yarnpkg

`yarn cache clean`

To fix this, run:

yarn cache clean
yarn add --dev jest

From the yarn cache documentation:

> ### yarn cache clean [<module_name...>] > Running this command will clear the global cache. It will be populated again the next time yarn or yarn install is run. Additionally, you can specify one or more packages that you want to clean.

You can also see where the cache is with yarn cache dir.

> ### yarn cache dir > Running yarn cache dir will print out the path where yarn’s global cache is currently stored.

Solution 2 - Yarnpkg

Yarn cache clean did not help. We must downgrading yarn version on the server.

It turns out that the problem is associated with the use of private packages.

GitHub Yarnpkg - "Incorrect integrity when fetching from the cache" #7584

Solution 3 - Yarnpkg

For anyone who is working with heroku and sees this error:

install heroku cli
login via heroku login
heroku plugins:install heroku-repo
heroku repo:purge_cache -a $YOURAPPNAME

then do a manual rebuild

Solution 4 - Yarnpkg

Clean the cache and reinstall:

yarn cache clean
yarn install -f

Solution 5 - Yarnpkg

You need to run these two commands before installing the package:

yarn config set unsafe-disable-integrity-migration false
yarn cache clean

Solution 6 - Yarnpkg

Tried to upgrade yarn and it solved my problem. It may be due to the compatibility issue

yarn policies set-version

Will download the latest stable release

Reference : yarn docs https://yarnpkg.com/lang/en/docs/cli/policies/#toc-policies-set-version

Content Type	Original Author	Original Content on Stackoverflow
Question	Doug Richardson	View Question on Stackoverflow
Solution 1 - Yarnpkg	Doug Richardson	View Answer on Stackoverflow
Solution 2 - Yarnpkg	Jogi	View Answer on Stackoverflow
Solution 3 - Yarnpkg	velop	View Answer on Stackoverflow
Solution 4 - Yarnpkg	Anayo Oleru	View Answer on Stackoverflow
Solution 5 - Yarnpkg	gildniy	View Answer on Stackoverflow
Solution 6 - Yarnpkg	Karan sharma	View Answer on Stackoverflow