Error AtlasError Documentation and Resolution
Back to searchMore npm errors

npm

npm hangs on Windows at addRemoteTarball

npm hangs on Windows at addRemoteTarball

npm can hang on Windows during addRemoteTarball when more than one tmp directory is configured in .npmrc.

npm hangs on Windows at addRemoteTarballinstallation

Observed message

npm hangs on Windows at addRemoteTarball

Why it happens

  • The npm configuration defines more than one tmp directory.
  • Conflicting temp directory settings cause npm to stall while processing tarballs.
  • A legacy .npmrc file carries redundant temp configuration.

How to fix it

  1. Inspect npm config output and look for multiple tmp definitions.
  2. Remove all but one tmp configuration entry from .npmrc.
  3. Retry the install after simplifying temp directory settings.

Official reference

npm Docs: Common errors

Related errors

cb() never called!npm cb() never called when using shrinkwrapped dependenciesENOGIT / not found: gitnpm could not find gitENOSPCnpm could not write because the drive is full or not writableEACCES permissions errornpm EACCES permissions error during global install

Explore more

npmBrowse more npm errorsinstallationBrowse more installation errors
npm hangs on Windows at addRemoteTarball: causes and fixes | Error Atlas