Error when starting Sonar analysis

[Colin]

Hey there.

@joaogamarra

2025-09-24T17:34:39.0000359Z 17:34:38.995 INFO  'sonar.scanner.skipNodeProvisioning' is set. Skipping embedded Node.js runtime deployment.
2025-09-24T17:34:39.0001483Z 17:34:38.996 INFO  Forcing to use Node.js from the host.
2025-09-24T17:34:39.0002057Z 17:34:38.999 INFO  Using Node.js executable: 'node'.

Hello,

From your logs, I see sonar.scanner.skipNodeProvisioning is set to true, which makes the scanner use your system’s Node.js instead of one embedded with the analyzer.

To resolve this, you have two options:

1. Remove the sonar.scanner.skipNodeProvisioning option so the embedded (supported) Node.js version is used.
2. Upgrade Node.js on your host to at least v20.12.0 and (if needed) configure the path using the sonar.nodejs.executable analysis parameter. Refer to the SonarQube documentation for more details.

It looks like Node.js 18 support was dropped without a clear announcement or updated documentation; I’m looking into that further.