npm ERR! code ETARGET — No matching version found for package@^9.9.9
The version range in package.json doesn’t match any published version of the package.
Exact message you may see
No matching version found forcode ETARGET
Seen on:
npm
Meaning
A typo in the version, a version that was never published (or was unpublished), or a private registry mirror that hasn’t synced the newest release.
Common causes
- Version doesn’t exist (typo, future version)
- Mirror/proxy registry out of date
- Dist-tag referenced that doesn’t exist
⚡ Quick fix
- Check published versions: npm view package versions
- Fix the range in package.json
- Point to the public registry or refresh the mirror
Detailed fix by platform
npm
npm view react versions --json | tail -5
How to diagnose
- Range — What does package.json request?
- Published — Which versions exist?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 0x8007007E 0x8007007E: The specified module could not be found
- Dependency requires compileSdk Dependency 'androidx.x:1.y' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs
- E401 npm ERR! code E401 — Unable to authenticate, need: Basic realm / Incorrect or missing password
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 12 Oct 2026