Ignores engines having valid range of supported Node.js versions

Warning: Due to “engines”: { “node”: “^18 || ^20 || ^22” } in your package.json file, the Node.js Version defined in your Project Settings (“20.x”) will not apply, Node.js Version “22.x” will be used instead. Learn More: Using the Node.js Runtime with Vercel Functions

  • Supported Node versions in my project are 18, 20 and 22
  • The selected version in Vercel settings is 20
  • But for some reason it decides to ignore the setting and use 22

Not a big issue, but still seems to be a bug

Hi, the engines property in the package.json takes precedence over the Project Settings. Since you have ^22 defined in the engines property, it will always search for the latest version of Node available in the Runtime.

Please let us know if you have any questions.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.