How to fix npm ERR! code EVERNOTPUBLISHED npm ERR! Version not published: package@1.0.0 in npm

npmBEGINNERMEDIUMUpdated Dec 6, 2025· 219 views

The version not published error occurs when you try to install a package version that doesn't exist in the npm registry. Verify the version exists, check for typos, or clear your npm cache if the version was recently published.

Quick fix

Fixes E404

npm view <package-name> versions
  1. Verify the version exists
  2. Check for typos
  3. Clear npm cache
  4. Use a version range instead
npm — error
npm view <package-name> versions
npm ERR! code EVERNOTPUBLISHED
npm ERR! Version not published: package@1.0.0

What this error means

This error occurs when npm cannot find the specific version of a package you're trying to install. The package might exist, but the particular version you requested isn't available in the registry. Common scenarios include: requesting a version that was unpublished (npm allows unpublishing within 72 hours of initial publish), typos in version numbers, or trying to install a version that was never actually released. The error can also appear when npm's cache is stale and doesn't reflect recent registry changes, or when accessing private packages without proper authentication.

Typical symptoms

  • npm install fails with 404 error for specific version
  • Error message shows the exact version that couldn't be found
  • Package exists but specific version doesn't
  • Recently published version not found immediately
  • Private package versions inaccessible
  • CI/CD pipeline fails for previously working version

Common causes

  1. Version was unpublished by the package maintainer
  2. Typo in version number in package.json
  3. Version was never actually published
  4. npm cache contains stale package metadata
  5. Private package authentication expired
  6. Registry sync delay for recently published versions
  7. Scoped package without proper access permissions

How to fix "npm ERR! code EVERNOTPUBLISHED npm ERR! Version not published: package@1.0.0"

1Verify the version exists

Check what versions are actually available:

bash
npm view <package-name> versions

This shows all published versions. If your requested version isn't listed, it doesn't exist.

2Check for typos

Common version typos:
- 1.0 instead of 1.0.0
- v1.0.0 instead of 1.0.0
- Wrong minor/patch number

Fix in package.json:

json
{
  "dependencies": {
    "package": "1.0.0"
  }
}
3Clear npm cache

If the version was recently published, clear your cache:

bash
npm cache clean --force
npm install

npm caches package metadata, which might be stale.

4Use a version range instead

If you don't need an exact version, use a range:

json
{
  "dependencies": {
    "package": "^1.0.0"
  }
}

This installs the latest 1.x.x version that exists.

5Check authentication for private packages

For scoped or private packages, ensure you're logged in:

bash
npm whoami
npm login

For organizations, verify your access:

bash
npm access ls-packages
6Wait for registry sync

If you just published the version, wait a few minutes. npm's CDN can take time to sync.

Check the registry directly:

bash
npm view <package-name>@<version>

If it returns data, the version exists and your cache is stale.

Advanced notes

npm's unpublish policy allows package owners to remove versions within 72 hours of publishing. After that, unpublishing requires contacting npm support. If a critical version disappears, check with the package maintainer or look for alternatives.

For enterprise environments with private registries (Verdaccio, Nexus, Artifactory), this error might indicate the version wasn't synced from the upstream registry. Check your registry's proxy/cache settings.

In CI/CD pipelines, use npm ci with a committed package-lock.json to ensure reproducible builds. This prevents issues where a version is available during development but later becomes unavailable.

If you're the package maintainer and accidentally unpublished, you can republish the same version within 24 hours. After that, you must increment the version number.

Frequently asked questions

What does "E404" mean?
This error occurs when npm cannot find the specific version of a package you're trying to install. The package might exist, but the particular version you requested isn't available in the registry. Common scenarios include: requesting a version that was unpublished (npm allows unpublishing within 72 hours of initial publish), typos in version numbers, or trying to install a version that was never actually released.
How do I fix "E404"?
The version not published error occurs when you try to install a package version that doesn't exist in the npm registry. Verify the version exists, check for typos, or clear your npm cache if the version was recently published.
What causes "E404"?
Version was unpublished by the package maintainer Typo in version number in package.json Version was never actually published
Is the "E404" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading