Unify node.js executable config


(Björn Kautler) #1

If node.js is not available in the PATH, you have to configure it.
For SonarCSS plugin you need to set the property sonar.css.node.
For SonarJS plugin you need to set the property sonar.nodejs.executable.
Imho it would make sense to unify this to depend on the same property, or do you think it would make sense to use different node.js versions for CSS vs. JS analysis?
If so, maybe the SonarJS name is too generic on the other hand?


(Elena Vilchik) #3

Indeed it’s in our plans to rely only on sonar.nodejs.executable. See ticket.

Thanks for feedback!