Node.js 14/16 support in SonarQube 2025.4

SonarQube Server / Community Build
,
1

Hello,

We are currently using SonarQube 10.8 and preparing to upgrade to SonarQube 2025.4 LTA.

Some of our services are still built and deployed with Node.js 14 and 16. From the documentation, it seems that support for Node.js 14 and 16 has been dropped, but it is not clear to us whether this refers to:

  • the Node.js runtime used by the SonarScanner / JavaScript analyzer when running the analysis (scanner environment), or
  • the Node.js versions (Node.js 14/16) used by the applications being analyzed (project runtime).

My questions are:

  1. When the documentation says that support for Node.js 14/16 has ended, which “environment” does this restriction apply to exactly?
    (e.g. the Node.js runtime used by the scanner vs the runtime of the application itself)

  2. If we make sure that the Node.js runtime used by the scanner is a supported version (e.g. the embedded Node.js or Node 20+), is it still fully supported to analyze projects that target Node.js 14/16?

I would like to hear from people who have experience with this.

2

When the documentation states that support for Node.js 14/16 has ended, it’s referring to the Node.js runtime used by SonarScanner during code analysis—not your project’s runtime environment. The important point is that the system where analysis runs needs a supported Node.js version installed, or uses the embedded Node.js provided by SonarQube for most architectures.

You can still analyze projects that target Node.js 14/16; the restriction only applies to the Node.js version used by the analysis tools themselves, not your application’s codebase. In most cases, SonarQube automatically handles this by downloading a compatible Node.js version as needed during analysis, so there’s usually nothing extra for you to configure.

1 Like