Hi. You can set the SONAR_NODEJS_PATH environment variable to fix this problem or add node’s location to PATH. We’ve noted that the settings are missing the ability to set this path, which I agree is not great in terms of UX. Automatic detection works by running where command, so maybe VS26 stopped adding its bundled node’s location to PATH?
I looked into the Output on VS 2022, where SonarQube works fine, and it logs the same thing.
[SLCore] Node.js could not be automatically detected, has to be configured manually in the SonarLint preferences!
The UI head notification occurring only very sparsely is a bit confusing if it can never find nodejs but works anyway.
I’ve seen the same UI message many times before in VS 2022 and maybe 2019 before that. At least on three separate occasions. I was always under the impression that SonarQube extension updates fixed some vs-internal-nodejs path resolution. But maybe it’s just that the msg shows only rarely in specific cases, and it never finds it?
It’s possible SonarQube works fine in VS 2026 despite the message too. I only tested VS2026 on a smaller newer project.