SonarQube for IDE (WebStorm) on Ubuntu 22.04 does not report JavaScript/TypeScript issues

SonarQube for IDE
1

Environment

  • OS: Ubuntu 22.04.5 LTS

  • IDE: WebStorm 2025.3.1.1, Runtime version: 21.0.9+10-b1163.86 amd64 (JCEF 137.0.17)
    VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

  • Plugin: SonarQube for IDE (SonarLint), version 11.10

  • Language: TypeScript / JavaScript

  • Node.js: 22 LTS (also tested other versions)

  • SonarQube Server: Issues are correctly detected on the server side

Problem Description

On Ubuntu 22.04, SonarQube for IDE does not report any JavaScript/TypeScript issues in WebStorm, even though:

  • The same project reports issues correctly on SonarQube Server

  • The same project reports issues correctly on macOS using the same IDE and plugin

  • Other analyzers (for example Dockerfile / IaC) work correctly on Ubuntu

The analysis completes without errors, but always reports 0 issues for JS/TS files.

Relevant Logs

On Ubuntu, the following lines always appear in the IDE log:

Miss the cache for 1 out of 1: RUNTIME_API_INCOMPATIBLE [1/1]

There are no logs indicating that JavaScript rules are loaded, for example no lines like:

Loaded xxx JavaScript rules

On macOS, these RUNTIME_API_INCOMPATIBLE lines do not appear, and issues are reported as expected.

Observed Behavior

  • JavaScript/TypeScript files are parsed

  • The bridge server runs

  • Text & Secrets analysis runs

  • Dockerfile / IaC analysis reports issues

  • JavaScript/TypeScript rules are not executed

  • Only the currently opened file is indexed

  • Result: 0 issues

Expected Behavior

SonarQube for IDE should report JavaScript/TypeScript issues on Ubuntu in the same way as:

  • SonarQube Server

  • SonarQube for IDE on macOS

Additional Notes

  • This issue persists even when using Node.js 22 LTS

  • WebStorm was installed without Snap (Snap was previously removed)

  • Clearing SonarLint caches and reconfiguring Node.js does not resolve the issue

  • The problem appears to be specific to the JavaScript analyzer runtime on Linux, as JVM-based analyzers (Dockerfile/IaC) work correctly

Question

Is RUNTIME_API_INCOMPATIBLE a known issue for the JavaScript analyzer in SonarQube for IDE on Linux (Ubuntu 22.04)?
Is there an officially supported workaround or recommended plugin version for this environment?

Thank you.

4

Hey @melOn, thanks for reaching out!

Could you please provide the full verbose logs of SonarQube for IDE? This will help us understand what is happening.

The RUNTIME_API_INCOMPATIBLE log should not have any impact on the analysis, and you can safely ignore it, as far as I can tell.

Could you also please provide the exact version of the Node.js you’re using? It would also be helpful to know about your SonarQube Server version.

Thank you!

5

hey @nicolas.quinquenel

Thank you for your message.

Please find the requested information below:

  1. SonarQube for IDE verbose logs
    [2026-01-23T07:37:57.886] [sonarlint-analysis-scheduler] INFO sonarlint - Index files
    [2026-01-23T07:37:57.887] [Report about progress of file indexation] INFO sonarlint - 1 file indexed
    [2026-01-23T07:37:57.903] [sonarlint-analysis-scheduler] INFO org.reflections.Reflections - Reflections took 9 ms to scan 1 urls, producing 24 keys and 257 values
    [2026-01-23T07:37:57.919] [sonarlint-analysis-scheduler] INFO org.sonar.iac.common.extension.IacSensor - There are no files to be analyzed for the Docker language
    [2026-01-23T07:37:57.92] [sonarlint-analysis-scheduler] WARN sonarlint - No workDir in SonarLint
    [2026-01-23T07:37:57.938] [nodejs-stream-consumer] INFO org.sonar.plugins.javascript.bridge.BridgeServerImpl - 1 source file to be analyzed
    [2026-01-23T07:37:57.938] [nodejs-stream-consumer] INFO org.sonar.plugins.javascript.bridge.BridgeServerImpl - 1/1 source file has been analyzed
    [2026-01-23T07:37:57.938] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.javascript.analysis.cache.CacheReporter - Hit the cache for 0 out of 1
    [2026-01-23T07:37:57.938] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.javascript.analysis.cache.CacheReporter - Miss the cache for 1 out of 1: RUNTIME_API_INCOMPATIBLE [1/1]
    [2026-01-23T07:37:57.938] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.javascript.analysis.CssRuleSensor - No CSS, PHP, HTML or VueJS files are found in the project. CSS analysis is skipped.
    [2026-01-23T07:37:57.938] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.common.TextAndSecretsSensor - Available processors: 12
    [2026-01-23T07:37:57.938] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.common.TextAndSecretsSensor - Using 12 threads for analysis.
    [2026-01-23T07:37:57.94] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.common.TextAndSecretsSensor - Start fetching files for the text and secrets analysis
    [2026-01-23T07:37:57.94] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.common.TextAndSecretsSensor - Retrieving all except binary files
    [2026-01-23T07:37:57.94] [sonarlint-analysis-scheduler] INFO org.sonar.plugins.common.analyzer.Analyzer - Starting the text and secrets analysis
    [2026-01-23T07:37:57.94] [Progress of the text and secrets analysis] INFO org.sonar.plugins.common.MultiFileProgressReport - 1 source file to be analyzed for the text and secrets analysis
    [2026-01-23T07:37:57.943] [Progress of the text and secrets analysis] INFO org.sonar.plugins.common.MultiFileProgressReport - 1/1 source file has been analyzed for the text and secrets analysis
    [2026-01-23T07:37:57.943] [sonarlint-analysis-scheduler] INFO sonarlint - Analysis detected 0 issues and 0 Security Hotspots in 99ms

  2. SonarQube Server version
    SonarQube Server version: [v25.12.0.117093]

  3. Node.js version:
    Node.js version currently in use: [v22.21.1]

If you need any additional logs or further details from our side, please let us know and we will be happy to provide them.

Thank you for your support.

6

Thank you for the information you’ve shared so far. I’ve looked into this further but haven’t been able to identify anything that clearly explains the issue.

Could you please provide the full verbose logs from SonarQube for IDE? We’re particularly interested in the logs captured right when the extension starts.

Additionally, if you have a small, reproducible code sample that demonstrates the problem, that would greatly help us narrow down and pinpoint the root cause.

Thanks!

7

hey @nicolas.quinquenel

Thank you for your message.

This is what I found.

Exception in thread “SonarLint Client RPC sequential executor”
java.lang.NullPointerException
ApplicationManager.getApplication() is null

8

Thanks @melOn, however these are still not the full verbose logs from our extension :sweat_smile:

We really need them to further investigate the issue, please follow our documentation. You can find the logs here:

image
image768×474 102 KB

You’d need to copy the whole log session and paste it there - or privately if you prefer.

Thank you :folded_hands: