[BUG] Integrity check fails for azure artifacts (and apparently other private registries) NPM packages
Problem
Current Behavior: We are trying to upgrate to NPM 7, but we run into problems with getting packages from azure artifacts. The following log is shown, when running `npm i --verbose`: [code block] Expected Behavior: I expect the packages to be downloaded correctly, just as they did using npm 6 Steps To Reproduce: Reference packages to azure artifacts in your package.json. Try to run `npm install` expected: packages install actual: error as shown above Environment: - OS: windows 10 - Node: v12.16.1 - npm: 7@beta10
Error Output
Error: sha1-ZTIGEke6SQtyObZXul6THKgWSz0= integrity checksum failed when using sha1: wanted sha1-ZTIGEke6SQtyObZXul6THKgWSz0= but got sha512-1HAETTUJsxZ0ZT/s/kYXiDJgmm4bXD7co77wzewb4t8BBW7Vhk0ONkOs5orSToPCtu4
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: [BUG] Integrity check fails for azure artifacts (and apparently other private registries) NPM packages
I'm also getting this with Gemfury's private registry, but the signature is a SHA512 in my case. Both NPM `6.14.6` and Yarn `1.22.5` work properly, but NPM `7.0.0-beta.10` is calculating a different signature and failing the integrity check.
Trust Score
3 verifications
- 1
I'm also getting this with Gemfury's private registry, but the signature is a SH
I'm also getting this with Gemfury's private registry, but the signature is a SHA512 in my case.
- 2
Both NPM `6.14.6` and Yarn `1.22.5` work properly, but NPM `7.0.0-beta.10` is ca
Both NPM `6.14.6` and Yarn `1.22.5` work properly, but NPM `7.0.0-beta.10` is calculating a different signature and failing the integrity check.
Validation
Resolved in npm/cli GitHub issue #1800. Community reactions: 2 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep