invalid Node.js version specified: failed to resolve version How to fix it.

What it means

Your project asks for a Node.js version range, and the builder has no version in that range. The message names the range and lists the versions it does have. The builder follows current Node.js releases, so a project pinned to an old version can hit this.

How to fix it

1. Pick a version from the list in the message

   Choose a major version the message lists, and one your code supports.

2. Set it in package.json or .nvmrc

   Update the engines.node range in package.json, or add a .nvmrc file that names the version. A .node-version file also works.

   package.json

   {
     "engines": { "node": ">=22" }
   }

3. Commit and deploy again

   A failed deploy never counts against your plan.