Hi,
This problem may occurs when using older versions of our JS/TS analyzer.
Are you using connected mode to SonarQube? If yes, could you provide the version of the JS/TS analyzer installed on your SonarQube server?
A workaround is to ensure IntelliJ is started with an environment where Node is in the PATH. There is also a property you can set (see SonarTS unable to start - Node not found).