Programming language you’re coding in: Javascript / Typescript
Is connected mode used:
SonarQube Server
I am experiencing an issue where SonarLint does not show any warnings for JavaScript or TypeScript files, even in a simple project. I try to use sample file test Python from sonar and it works correctly. I have already tried a full reinstall of VS Code and the extension, and have explicitly set the path to Node.js, but the problem continues. Its sometimes happen before, and solved by re-open the VS Code because i think the problem was on large file that has so many lines. But today i tried that solution again and doesnt work, in local sometimes doesnt show same warning like on the sonarqube website.
The console on VS Code doesnt show any error, here 1 error that exist after i try so many times to reopen the project
TypeError: Cannot read properties of undefined (reading ‘label’)
at s. (c:\Users\Hype G12.vscode\extensions\sonarsource.sonarlint-vscode-4.26.0-win32-x64\dist\extension.js:2:1732622)
…
Hello @slmnfz, welcome to Sonar Community, and thanks a lot for reporting this behavior!
Would you be able to share your logs with us? And could you also share what version of Node.js executable is SonarQube for IDE using (You should see the log looking like detected node version: x.y.z
Hello everybody,
I’m encountering the same issue described by slmnfz and I have the same technical confuguration. My java version:
java version “17.0.13” 2024-10-15 LTS
Java™ SE Runtime Environment (build 17.0.13+10-LTS-268)
Java HotSpot™ 64-Bit Server VM (build 17.0.13+10-LTS-268, mixed mode, sharing)
Initially, I was using Node.js version 18.18.0, and just tried updating to 18.20.8, but now I’m seeing different errors in the Output tab:
I believe your issue is different - the errors indicate that the issue storage for SonarQube for IDE has been corrupted. To get out of this, you can try deleting the following folders
Does anyone know which “SonarQube for IDE” version is fully compatible with node 18.18.0?
You can downgrade SonarQube for IDE version to 4.25.1 and it should work with Node 18.18 (once you fix the data corruption problem above). But 18.20 will also work with 4.26 again, if the above problem is resolved.
As a rule of thumb, the latest NodeJS LTS will always work with the latest SonarQube for IDE version.
Sorry for my late reply, i was using Node version 18.17.1.
the issues was already solved when i try to downgrade the sonarqube version into 4.25.1, i dont notice i was enable the auto update for vs code extension.
