npm install fails with 'npm ERR! code ETARGET — No matching version found for package@^x.y.z' (or 'notarget'). Why, and how do I fix it?

Cause: npm looked up the package in the registry and no published version satisfies the version range in package.json or the command. Usual reasons: a typo in the version, or a version that was never published (or was unpublished or deprecated-and-removed); a range written for a newer major that doesn't exist yet; a dist-tag that points elsewhere; a brand-new release that hasn't reached your registry mirror or cache yet; or your npm is pointed at a different registry (a company proxy or a scoped registry) that doesn't have that package or version. Fix: 1. See what actually exists: npm view <package> versions (and npm view <package> dist-tags) shows published versions and tags in the registry npm is using. 2. Fix the range to one that exists (edit package.json, or npm install <package>@<real-version>), then regenerate the lockfile. 3. Check which registry is used: npm config get registry and any @scope:registry lines in .npmrc; a private mirror may not have proxied the version yet, so try again later or ask the registry admins to sync it. 4. For a just-published version, clear stale metadata: npm cache verify (or npm cache clean --force as a last resort) and retry. 5. If a dependency of a dependency requests a missing version, update the parent package, or use overrides in package.json to point at an existing version and test. 6. Watch for typosquatting when a name 'doesn't exist': confirm the exact package name on the registry's website before installing a look-alike. Verify: npm view <package>@<range> version returns a version, and npm install completes. Sources: https://docs.npmjs.com/cli/v10/commands/npm-view https://docs.npmjs.com/cli/v10/using-npm/registry