By default, a new project uses the latest Node.js LTS version available on Vercel.
Current available versions are:
Only major versions are available. Vercel automatically rolls out minor and patch updates when needed, such as to fix a security issue.
To override the default version and set a different Node.js version for new deployments:
You can define the major Node.js version in the engines#node
section of the package.json
to override the one you have selected in the Project Settings:
{
"engines": {
"node": "22.x"
}
}
For instance, when you set the Node.js version to 18.x in the Project Settings and you specify a valid semver range for Node.js 22 (e.g. 22.x
) in package.json
, your project will be deployed with the latest 22.x version of Node.js.
The following table lists some example version ranges and the available Node.js version they map to:
Version inpackage.json
Version deployed >=20.0.0
>=18.0.0
>=16.0.0
latest 22.x version 22.x
^22.0.0
latest 22.x version 20.x
^20.0.0
latest 20.x version 18.x
^18.0.0
latest 18.x version
To verify the Node.js version your Deployment is using, either run node -v
in the Build Command or log process.version
.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4