VSCode SonarLint org.sonarsource.nodejs.NodeCommandException: Failed to start server (60s timeout)

SonarLint VS Code
, ,
1
  • Version used:
    SonarLint (sonarsource.sonarlint-vscode) v1.18.0
  • error observed
[Error - 08:25:24.927] org.sonarsource.nodejs.NodeCommandException: Failed to start server (60s timeout)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServer(EslintBridgeServerImpl.java:118)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServerLazily(EslintBridgeServerImpl.java:163)
	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.startBridge(AbstractEslintSensor.java:137)
	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.execute(AbstractEslintSensor.java:111)
	at org.sonar.plugins.javascript.eslint.TypeScriptSensor.execute(TypeScriptSensor.java:55)
	at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.executeSensor(SensorsExecutor.java:80)
	at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.execute(SensorsExecutor.java:71)
	at org.sonarsource.sonarlint.core.container.analysis.AnalysisContainer.doAfterStart(AnalysisContainer.java:132)
	at org.sonarsource.sonarlint.core.container.ComponentContainer.startComponents(ComponentContainer.java:126)
	at org.sonarsource.sonarlint.core.container.ComponentContainer.execute(ComponentContainer.java:111)
	at org.sonarsource.sonarlint.core.container.standalone.StandaloneGlobalContainer.analyze(StandaloneGlobalContainer.java:153)
	at org.sonarsource.sonarlint.core.StandaloneSonarLintEngineImpl.analyze(StandaloneSonarLintEngineImpl.java:90)
	at org.sonarsource.sonarlint.ls.AnalysisManager.lambda$analyzeStandalone$5(AnalysisManager.java:323)
	at org.sonarsource.sonarlint.ls.AnalysisManager.analyzeWithTiming(AnalysisManager.java:365)
	at org.sonarsource.sonarlint.ls.AnalysisManager.analyzeStandalone(AnalysisManager.java:323)
	at org.sonarsource.sonarlint.ls.AnalysisManager.analyze(AnalysisManager.java:248)
	at org.sonarsource.sonarlint.ls.AnalysisManager.lambda$analyzeAsync$0(AnalysisManager.java:207)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
  • steps to reproduce
    I’ve just opened a ts file (Angular component) and started to code, after saving the error was generated
2

Hello, welcome to the community! And thank your for your report.

Which OS are you using? Is the Node.js executable available on the %PATH% or do you configure it explicitly in VSCode’s settings?

In the past, we got similar reports on Windows from people who had another tool’s node.exe taking precedence over the one from Node.js, maybe you’re hitting a similar situation.

3

Hello Jean, I’m using Windows 10 with node.js on the path.

4

Hello, thank you for your patience.

Do you know how big your project is in terms of number of files / lines of code? How many tsconfig.json files does it use?

We have seen in other reports that in some cases, the TS compiler used under the hood by the TS analyzer seems to hit a performance hotspot. We have not identified yet where it lies, so any additional data is helpful for us.

1 Like