npm / npm/cli

[BUG] No Debug Information in `Integrity checksum failed` Error

Open
#2,955 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Release 7.x
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

Current Behavior:

Error message doesn't give ANY relevant details. What integrity checksum failed? Assuming this is related to a package, which package was this related to? What download URL produced the checksum output we got?

There is NOTHING in this error message to help me debug this.

npm ERR! code EINTEGRITY
npm ERR! Integrity checksum failed when using sha512: wanted sha512-cE1jYr2dEg1wBImvXlNtp0xDoS79rfEdGozQVgliDZj1uERH4k+rmEMTudP9b4VQ8O6nRb5gPqft0QzEQGMQgA== but got sha512-mkv/s9Q6ieanbiaYUvxxC765JuR+OLTojYj16UaGRX92FxM2XWb/lfqKrukSBJ47hmYv0Bhm57DXOpb/cGxdbA==.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/charliefish/.npm/_logs/2021-03-25T02_31_01_025Z-debug.log
Expected Behavior:

Error message to give relevant details

Steps To Reproduce:
  1. Produce Integrity checksum failure (not quite sure how to do this manually)
  2. Notice how error doesn't give any debug information
Environment:
  • OS: macOS 11.3 Beta (20E5217a)
  • Node: v15.11.0
  • npm: 7.6.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the integrity checksum failure from the reported npm CLI environment and trace the resulting error context. Done means the error identifies the affected package and download URL, alongside the checksum details.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.