Hello, thanks for your message.
Unfortunately, this is not the case. The JavaScript/TypeScript analyzer embedded by SonarLint will try to run the node executable:
- either from the
sonar.nodejs.executableproperty (see Settings > Tools > SonarLint > Project Settings)
- or directly from the
PATHenvironment variable
Using the one set in the “Node.js and NPM” settings could be a nice UX improvement; however it would be only available when the Node.js integration plugin is installed, which is not necessarily the case.
