Error AtlasError Documentation and Resolution
Back to searchMore npm errors

npm

npm registry returned 404 or server error

npm ERR! Error: 404 Not Found

npm can fail with 404 or 500 responses when the registry is temporarily unhealthy, the package tarball path is unavailable, or a published package is corrupt.

404 Not Found / Server errorregistry

Observed message

npm ERR! Error: 404 Not Found

Why it happens

  • The npm registry is experiencing a temporary glitch.
  • The requested tarball path is unavailable.
  • The published package or version may be corrupt.

How to fix it

  1. Check npm registry status and retry later.
  2. If the error persists for a specific package, verify that the package version still exists.
  3. Contact the package owner if the published artifact appears to be corrupt.

Official reference

npm Docs: Common errors

Related errors

Error: Invalid JSON / Unexpected token <npm registry response produced invalid JSONcb() never called!npm cb() never called when using shrinkwrapped dependenciesENOGIT / not found: gitnpm could not find gitENOENTnpm could not read package.json

Explore more

npmBrowse more npm errorsregistryBrowse more registry errors
npm registry 404 Not Found or server error: causes and fixes | Error Atlas