npm ERR! code E404

The requested package does not exist or has been unpublished from the npm registry.

Frequently documented in developer and vendor support forums.

• Typo in package name
• Package was unpublished
• Private package without authentication

1. Check package name spelling
2. Search npmjs.com for correct package name
3. Authenticate with npm login for private packages

Last reviewed: March 2026 How we review solutions

npm returns a 404 status code when the registry server confirms that the requested package does not exist at the URL npm constructed. This is an HTTP-level response, not a file system error—npm successfully connected to the registry, sent a request, and the registry replied "not found." The most common cause is a typo in the package name: npm's public registry has over two million packages, and a single misplaced character (e.g., "react-router-domm" instead of "react-router-dom") will produce a 404. Scoped packages present a different risk: if you reference @myorg/utils but have not authenticated with the private registry that hosts it, npm falls back to the public registry where @myorg/utils does not exist. Unpublished packages are another source—npm allows maintainers to unpublish within 72 hours, and after that the name is reserved but returns 404. Corporate environments that use a registry proxy (Verdaccio, Artifactory, Nexus) may return 404 if the proxy's upstream is misconfigured or the package has not been cached yet. Always start by verifying the exact package name on npmjs.com before investigating registry configuration.

1. Copy the exact package name from the error and search it on npmjs.com
2. Check for typos, especially transposed letters or missing hyphens
3. If scoped (@org/pkg), verify you are authenticated: npm whoami --registry=URL
4. Inspect .npmrc for registry overrides that might redirect requests
5. Try npm view package-name to confirm the package exists on the configured registry

Package unpublished within 72-hour window

npm allows unpublishing packages less than 72 hours old. If you depended on a recently published package that was then unpublished, your lockfile still references it. Pin to an alternative package or wait for the author to republish.

Registry mirror lag

Corporate proxies like Verdaccio or Artifactory cache packages from the public registry. A brand-new package may not appear on the proxy for minutes or hours. Bypass the proxy temporarily or trigger a manual cache refresh.

GitHub Packages registry confusion

GitHub Packages uses a different registry URL (npm.pkg.github.com). If your .npmrc points to GitHub Packages for all packages instead of just scoped ones, public packages will return 404.

Can unpublished packages be recovered?

No, once unpublished, the package name is reserved for 24 hours then becomes available.

How do I find alternative packages?

Search npmjs.com or use npms.io to find similar packages.

How do I check if a package was unpublished?

Visit npmjs.com/package/package-name. If the page says "not found" but you know it existed before, it was likely unpublished. Check the npm status blog or GitHub issues for the package.

Why does E404 happen only in CI but not locally?

Your CI environment may use a different registry (corporate proxy, GitHub Actions cache) or a different .npmrc file. Compare the registry URL in CI logs against your local npm config get registry output.

Can I install a package directly from a Git repository instead?

Yes. Use npm install github:user/repo or npm install git+https://github.com/user/repo.git to bypass the registry entirely. This works for public repositories and private ones if you have Git credentials configured.

• npm install – Official npm Docs
• package.json Reference – npm Docs