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
-
Check which versions exist
Run
npm view react-hot-toast versionsto list the published versions, with your package name in place of the example. -
Change the range
Use a version that exists, or a range that includes one, such as
^2.4.0. -
Run
npm installand commit the lock fileA 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.