Error in SonarLint for IntelliJ SonarLint not finding Node.js

SonarQube for IDE IntelliJ Platform
,
1

This message was auto-generated. I really don’t have a clue at this point. I am brand new to this community. I know that system was reporting that I could not find the Node.js even though I installed node and pointed the program to the folder C:\Program Files\Nodejs

Environment:

  • Java: JetBrains s.r.o. 11.0.12
  • OS: Windows 10 amd64
  • IDE: PhpStorm 2021.2.3
  • SonarLint: 6.3.0.39716
java.lang.NullPointerException
	at o.sl.ij.config.global.ServerConnectionMgmtPanel.dispose(ServerConnectionMgmtPanel.java:361)
	at c.ij.oa.util.ObjectTree.runWithTrace(ObjectTree.java:136)
	at c.ij.oa.util.ObjectTree.executeAll(ObjectTree.java:166)
	at c.ij.oa.util.Disposer.dispose(Disposer.java:155)
	at c.ij.oa.util.Disposer.dispose(Disposer.java:143)
	at o.sl.ij.config.global.SonarLintGlobalConfigurable.disposeUIResources(SonarLintGlobalConfigurable.java:146)
	at c.ij.oa.options.ex.ConfigurableCardPanel.dispose(ConfigurableCardPanel.java:153)
	at c.ij.oa.options.ex.ConfigurableCardPanel.dispose(ConfigurableCardPanel.java:35)
	at java.base/java.util.IdentityHashMap.forEach(IdentityHashMap.java:1354)
	at c.ij.ui.CardLayoutPanel.removeAll(CardLayoutPanel.java:206)
	at c.ij.ui.CardLayoutPanel.dispose(CardLayoutPanel.java:57)
	at c.ij.oa.options.ex.ConfigurableCardPanel.dispose(ConfigurableCardPanel.java:214)
	at c.ij.oa.util.ObjectTree.runWithTrace(ObjectTree.java:136)
	at c.ij.oa.util.ObjectTree.executeAll(ObjectTree.java:166)
	at c.ij.oa.util.Disposer.dispose(Disposer.java:155)
	at c.ij.oa.util.Disposer.dispose(Disposer.java:143)
	at c.ij.oa.ui.DialogWrapper.close(DialogWrapper.java:466)
	at c.ij.oa.ui.DialogWrapper.close(DialogWrapper.java:471)
	at c.ij.oa.ui.DialogWrapper.doOKAction(DialogWrapper.java:1078)
	at c.ij.oa.options.newEditor.SettingsDialog.applyAndClose(SettingsDialog.java:203)
	at c.ij.oa.options.newEditor.SettingsDialog.doOKAction(SettingsDialog.java:191)
3

Hello Sherwin,

Welcome to the community and thanks for raising this issue.

This is something we have already identified a few days ago, you can find the corresponding ticket here.

I can’t say exactly when the fix will land as we have higher priorities on other topics at the moment. You can track the progress on the ticket if you are interested.

Thanks
Damien