Update: After further investigation, I've found that this issue specifically occurs with the 64-bit Windows MSI installer and not the 32-bit MSI installer.
I have attempted all of the recommended solutions provided in other responses:
- Delete package-lock.json (file does not exist)
- Delete node_modules directory (no improvement)
- Run 'npm cache verify' command (message indicates "corrupted content removed" every time)
- Force clean npm cache using 'npm cache clean --force' (no change)
- Delete 'AppData/Local/npm-cache' directory (issue persists)
- Delete 'AppData/Roaming/npm' directory (problem remains)
- Reinstall npm globally with 'npm i -g npm' (no success)
- Set 'package-lock' configuration to false (no effect)
- Performed fresh installations of Windows 10 and 11 (did not resolve the problem)
- Disabled auto-proxy settings (issue unchanged)
The failure consistently occurs for [email protected]. I am at a loss for what steps to take next, as this prevents me from installing Angular CLI successfully.
- What is the expected sha512 checksum for [email protected]?
- Is there a way to disable EINTEGRITY checks?
- Are there any other potential solutions that I may have overlooked?
$ npm i npm WARN tarball tarball data for [email protected] (sha512-qTjK4MWnYtQHCMGg2qDUqeFYXfVvYq5qJkQTIsOV4VZCknoYePVaDTG9ygEB9Ct0kc0DWs7IrS6Ja+GjY62Kzw==) appears to be corrupted. Retrying installation...
... multiple instances of "appears to be corrupted"
npm WARN tarball tarball data for [email protected] (sha512-TCTIul70LyWe6IJWT8QSYeA54WQe8EjQFU4wY52Fasj5UKx88LNYKCgBEHcOMOrFF1rKGbD8v/xcNWVUq9SymA==) seems to be corrupted. Retrying installation...
npm ERR! code EINTEGRITY npm ERR! sha512-TCTIul70LyWe6IJWT8QSYeA54WQe8EjQFU4wY52Fasj5UKx88LNYKCgBEHcOMOrFF1rKGbD8v/xcNWVUq9SymA== integrity check failed for sha512: expected sha512-TCTIul70LyWe6IJWT8QSYeA54WQe8EjQFU4wY52Fasj5UKx88LNYKCgBEHcOMOrFF1rKGbD8v/xcNWVUq9SymA== but received sha512-U0dCcrUYPNLvBHhB3AuhIqz7zrcg2z2u5LCqmZVNN/aUqimo+p2cVyQ1kFsbc9XMmh8tNFcOkuY0itp0Yz31fQ==. (11280693 bytes)
npm ERR! Detailed log of this operation can be found at: npm ERR! C:\Users\chuck\AppData\Local\npm-cache_logs\2022-02-10T02_23_03_444Z-debug-0.log
Additionally, whenever I verify my cache, it detects new files as corrupted and deletes them automatically.
c:\Users\chuck\git\test>npm cache verify Cache verification completed successfully (~\AppData\Local\npm-cache_cacache) Verified content: 45 files (10072506 bytes) Index entries: 70 Completed in 0.151 seconds
c:\Users\chuck\git\test>npm cache verify Cache verification completed successfully (~\AppData\Local\npm-cache_cacache) Verified content: 44 files (10066799 bytes) Corrupted content removed: 1 file Garbage-collected content: 1 item (5707 bytes) Missing content: 2 files Index entries: 68 Completed in 0.188 seconds
c:\Users\chuck\git\test>npm cache verify Cache verification completed successfully (~\AppData\Local\npm-cache_cacache) Verified content: 40 files (9155292 bytes) Corrupted content removed: 4 files Garbage-collected content: 4 items (911507 bytes) Missing content: 6 files Index entries: 62 Completed in 0.178 seconds
c:\Users\chuck\git\test>npm cache verify Cache verification completed successfully (~\AppData\Local\npm-cache_cacache) Verified content: 37 files (8712984 bytes) Corrupted content removed: 3 files Garbage-collected content: 3 items (442308 bytes) Missing content: 4 files Index entries: 58 Completed in 0.155 seconds
It almost feels like the sha512 values are being generated randomly each time.