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.
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.
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.
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.
Hello @Hendrik_Iben, once again, I apologize for the lack of reply. We haven’t been able to reproduce this issue, and we did not receive any feedback from other users about this.
In any case, I created a ticket on our side to track this issue.
In the meantime, have you noticed anything else that might help explain this behavior? I’ll be taking another look over the next few days, hopefully with fresh eyes. I also suspect that our Node.js-related logic could be made more robust.
I’ll keep you updated if I find anything relevant.
Hi @nicolas.quinquenel. For a while, the issue did not occur on my side but in the last days it started to happen again. I do not see any pattern but I frequently change the project I am working on and open/close IntelliJ windows. Some of the projects are bound to to a SonarQube server and others are not - I have a suspicion that this happens when both types of projects are open at the same time but I could not reliably reproduce it yet.
Hey @Hendrik_Iben, just a quick update as we’ve released SonarQube for IntelliJ version 12.1. In this version, I improved the reliability of how we detect the Node.js version. We didn’t identify a specific bug in the logic, but there were cases where user could have changed the Node.js path without noticing it, which might have caused the issue.
Could you let us know if you’re still able to reproduce the problem with this version? For now, I’ll pause the investigation on our side.
Thank you for your efforts! I have not seen this issue again after the recent updates. There have also been some local changes here so some uncertainty remains - fingers crossed.
