This guide explains why it is important to use a recent version of Node.js for your application and how to select a more recent version with a Node.js site hosted on the Infomaniak infrastructure.

Preamble

• Node.js = official name of the language/environment.
• NodeJS = "technical" or simplified name in certain contexts (often for practical reasons, no real technical difference).

Is an outdated version of Node.js dangerous?

When you use a version of Node.js that is approaching the end of its support, a warning message appears in the dashboard of the affected site.

The Node.js runtime is regularly updated: each new version brings performance, security improvements, and support for recent features. Using a version that is no longer maintained exposes you to security risks and operational issues with other components. Malicious individuals could exploit known vulnerabilities in these versions to compromise your application. It is therefore strongly recommended to use a recent and officially supported version.

Three situations are possible:

• Fully supported version: no action required
• Version with security support only: it is recommended to switch to a more recent version
• Outdated version: it is strongly recommended to update to a more recent version

Using a more recent version of Node.js

The most recent versions of Node.js offer better performance and more stable behavior for your modern applications.

Before modifying the version used

• If your application uses a specific framework or library (Next.js, Express, etc.), check the proper support of the targeted version of Node.js.
• If your code was custom-developed, consult the official Node.js documentation to identify the changes made (deprecated APIs, module management, etc.).

What if a problem occurs?

If your application does not work correctly after changing the version of Node.js, you can revert to a previous version (if it is still supported) via the Advanced settings tab of the affected site.