Docs menu
Runtime versions
Choose your Node.js version with engines.node in package.json, and upgrade it safely.
On this page
Primcloud installs the Node.js version engines.node in your package.json asks for. The versions you can install are part of the Primcloud Runtime. Node.js 22, 24, and 26 are supported, following the Node.js release schedule; older and odd-numbered releases still install, with an end-of-life warning in the build log. Each deployment's build log shows the exact version it installed.
| Version | Status |
|---|---|
| Node.js 22 | Supported |
| Node.js 24 | Supported |
| Node.js 26 | Supported, installed when engines.node is unset |
Choosing a version#
Set engines.node in package.json to a semver range. The build installs the newest version that matches.
{
"engines": {
"node": "24.x"
}
}
"24.x": the newest 24 release. Recommended, since you get patch updates."^24.5.0": the newest 24 release from 24.5.0 on."~24.5.0": the newest 24.5 release."24.5.1": exactly 24.5.1."22.x || 24.x": either major, useful while migrating.
Ranges work like any npm dependency range; see semver.npmjs.com.
With engines.node unset, you get the recommended LTS, and the build log says so. Set a range so a rebuild can't move you to a new major unexpectedly.
A range that matches no Node.js release fails the build with "Unknown Node.js version".
Upgrading#
Change the range in package.json (from "24.x" to "26.x", say), commit, and push. The first build on the new version takes a little longer while it's downloaded.
Before moving to a new major:
- Native modules rebuild against the new version. If a dependency doesn't support it yet,
npm cifails. - Read the breaking changes in the Node.js changelog.
End-of-life versions#
Builds on a Node.js version past its end-of-life keep working, with a warning in the build log that a later update will turn it into a build error. Upgrade to a supported version before then to avoid an upgrade under pressure.