tarball corrupted 📦 npm

npm WARN tar TAR_ENTRY_ERROR / npm ERR! tarball data for x seems to be corrupted

A downloaded package tarball is damaged — cache corruption or a network/proxy problem.

Seen on: npm

Meaning

Interrupted downloads and proxies rewriting responses corrupt cached tarballs.

Common causes

  • Corrupted npm cache
  • Proxy altering downloads
  • Disk full during install

⚡ Quick fix

  1. npm cache clean --force
  2. Reinstall
  3. Check disk space and proxy

Detailed fix by platform

npm

  1. npm cache clean --force && rm -rf node_modules && npm install

How to diagnose

  1. Cache — Does a clean cache fix it?
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.