SonarQube plugin 'forgets' Node.js path every few days

SonarQube for IDE IntelliJ Platform
1

Please provide

  • Operating system: Windows 11
  • SonarQube for IntelliJ plugin version: 11.12.0.84088
  • IntelliJ version: 2025.3.2
  • Programming language you’re coding in: Java
  • Is connected mode used:
    • SonarQube Server: 2025.1.4

Every few days the SonarQube Plugin will tell me that my Node.js version is too low and when I check the settings I see that it a path to an older Node.js version (v18) is configured. I configure the correct path (v22) and it works for a few days before the cycle begins again.

sonar_node
sonar_node622×135 14.5 KB

I don’t understand why the setting changes or how I can provide the correct path in advance.

Is there some environment variable or setting I can configure to make it always use the correct path?

2

Hi,

Could you enable verbose logging and give us a log from IDE startup? Ideally it would include this error message, but I don’t want to ask you to log at that level for days.

 
Thx,
Ann

3

I enabled verbose logging and ‘luckily’ the issue appeared again after restarting the IDE.
This is the part of the log where the Node.js version is checked. I can also post the full log if earlier messages would help more:

 [2026-02-04T08:06:13.457] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Node.js path provided by configuration: C:\Users\iben\node-v18.20.4\node.exe
 [2026-02-04T08:06:13.457] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Checking node version...
 [2026-02-04T08:06:13.462] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Execute command 'C:\Users\iben\node-v18.20.4\node.exe -v'...
 [2026-02-04T08:06:13.602] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Command 'C:\Users\iben\node-v18.20.4\node.exe -v' exited with 0
stdout: v18.20.4
 [2026-02-04T08:06:13.633] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Plugin 'JavaScript/TypeScript/CSS Code Quality and Security' requires Node.js 20.12.0 while current is 18.20.4. Skip loading it.
 [2026-02-04T08:06:13.656] [SonarLint Server RPC sequential executor] DEBUG sonarlint - Plugin 'Go Code Quality and Security' is excluded because language 'GO' is not enabled. Skip loading it.

I have set up the correct Node.js path yesterday.

The machine is configured to have a more recent Node.js version (v22) in the system path but it seems this has no effect on the selection here.

1 Like
5

Hi,

Great news! :sweat_smile:

I’ve flagged this for the team.

 
Ann

7

Hey @Hendrik_Iben, I haven’t found yet a reason for this issue, but I’m continuing to investigate.

Could you please confirm whether you are using IntelliJ or WebStorm?

Also, have you noticed anything that might explain the settings reset? For example:

  • opening the SQ:IDE settings and saving a new value
  • modifying the Node.js path in your environment variables
  • switching between different Node.js versions
  • something else?

Thanks!

8

Hi @nicolas.quinquenel . I am using IntelliJ.

I have not yet found a pattern that triggers the issue but I think I have seen it more often when I open multiple projects were only some of them are bound to a project on the SonarQube server. Not sure if that is related.

I have not changed anything Node.js related on the system after setting up the v22 installation.

Best regards,
Hendrik