Blognpm

npm error No matching version found How to fix it.

No published version of a package matches the range in your package.json. This is usually a typo, or a version that has not been released.

How the Agent API works
What you see
npm error code ETARGET
npm error notarget No matching version found for react-hot-toast@^9.9.9.
npm error notarget In most cases you or one of your dependencies are
npm error notarget requesting a package version that doesn't exist.
  • What it meansThe version does not exist
  • Fix oneCheck the version on npm
  • Fix twoCheck the spelling
  • Thennpm install, commit the lock file

What it means

Your package.json asks for a package at a version range, and no published version fits it. The message names the package and the range. This is usually a typo in the version, or a package that has not shipped that release yet.

How to fix it

  1. Check which versions exist

    Run npm view react-hot-toast versions to list the published versions, with your package name in place of the example.

  2. Change the range

    Use a version that exists, or a range that includes one, such as ^2.4.0.

  3. Run npm install and commit the lock file

    A failed deploy never counts against your plan.

Why it happens

Coding agents sometimes write a version number from memory, or one that has not been published. The version looks plausible and does not exist.

01Questions

Version questions, answered.

Anything else? Write to us and a person answers.

support@antideploy.com
Is it the package name or the version?

If the package does not exist at all, you get a different error. See package not in this registry.

Does this failed deploy cost anything?

No. Failed deploys never count against your plan.

What range should I use?

A caret range such as ^2.4.0 accepts any 2.x version from 2.4.0 upward. Pick the newest version that exists and works with your code.

Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

Start from GitHub or a folder
Prompt copied Paste it into Claude Code, Codex or Cursor and press Enter.