npm ERR! code ETARGET

npm cannot find a package version that matches your version constraints.

Frequently documented in developer and vendor support forums.

• Version range too restrictive
• Package version does not exist
• Outdated package.json requirements

1. Check available versions with npm view package versions
2. Update version range in package.json
3. Use latest stable version

Last reviewed: March 2026 How we review solutions

ETARGET means npm queried the registry for a package and found it exists, but no published version satisfies the version range specified in your package.json or package-lock.json. This is different from E404 (package not found)—ETARGET means the package exists but the specific version you want does not. The most common cause is a typo in the version range: specifying "^99.0.0" or "~5.0.0" when the latest published version is 4.x. Another frequent trigger is a lockfile that references an unpublished version—npm authors occasionally unpublish pre-release or broken versions, leaving lockfile entries pointing to versions that no longer exist. Dependency resolution conflicts can also produce ETARGET: if package A requires "lodash@^4.17.0" and package B requires "lodash@^5.0.0" but lodash 5 does not exist yet, npm cannot satisfy both constraints. Corporate registry proxies that are not fully synced with the public registry may return a subset of available versions, causing ETARGET for versions that exist publicly but have not been cached by the proxy yet.

1. Check available versions: npm view package-name versions
2. Compare the requested version range with available versions
3. Delete package-lock.json and run npm install to regenerate
4. Check for typos in the version range in package.json
5. If using a proxy registry, verify it has the latest versions cached

Unpublished pre-release version in lockfile

Package authors sometimes publish and then unpublish alpha or beta versions. If your lockfile references an unpublished version, delete package-lock.json and run npm install to resolve to an available version.

Dist-tag pointing to non-existent version

npm packages can have custom dist-tags (like next, canary, beta). If the tag was updated or removed, npm install package@tag may return ETARGET. Check available tags with npm dist-tag ls package-name.

Verdaccio proxy with incomplete version cache

Verdaccio caches package metadata on first request. If the cache is old, newer versions are not listed. Access the Verdaccio admin panel and clear the cache for the affected package, or bump the cache TTL configuration.

How do I see all package versions?

Run npm view package-name versions to list all published versions.

What version syntax should I use?

Use ^1.0.0 for compatible updates or ~1.0.0 for patch updates only.

How do I find the latest version of a package?

Run npm view package-name version for the latest stable version, or npm view package-name versions for all published versions. You can also check the package page on npmjs.com for the full version history.

What does the caret (^) in version ranges mean?

The caret allows updates that do not modify the leftmost non-zero digit. ^1.2.3 means >=1.2.3 <2.0.0. ^0.2.3 means >=0.2.3 <0.3.0. If the specified major version does not exist, npm returns ETARGET.

Can I install a specific commit or branch instead of a version?

Yes. Use npm install user/repo#branch or npm install user/repo#commit-sha to install directly from Git. This bypasses version resolution entirely and is useful when you need a fix that has not been published yet.

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