Upgrade Node Version
Customers control which version of Node.js is used to run a Managed Runtime environment. Every two years, customers must upgrade Node.js versions, as support for older versions is removed to maintain security.
Support date definitions
- End of Life: Customers will no longer be able to deploy bundles using this version of Node.js after this date.
- Deprecation: Customers will start seeing a warning that a Node.js version upgrade will be required in the future for uninterrupted deployments.
- Availability: When this version of Node.js was first supported.
The current recommended version is Node.js 16.
| Version | Availability date | Deprecation date | End of Life date |
|---|---|---|---|
| 16.x | March 3, 2023 | ||
| 14.x | September 18, 2021 | April 30, 2023 | |
| 12.x | September 18, 2021 | September 20, 2022 | November 14, 2022 |
To update an environment to the latest supported version of Node.js:
- Edit your project’s
package.jsonfile. - Update your packages to versions that are compatible with the latest supported version of Node.js.
- Update
ssrParameters.ssrFunctionNodeVersionto the latest supported version of Node.js. This attribute sets the version of Node.js used by Managed Runtime environments. - Update your local development environments, continuous integration servers, and anything that builds bundles to use the latest supported version of Node.js. Reinstall all of your project's packages using the new Node.js version.
- Test that your project works as expected in a local development environment.
- Push a new bundle and deploy it to a non-production environment.
- Confirm that the environment works as expected.
- Deploy the new bundle to your production environment.