Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NodeJS location #5

Open
remycx opened this issue Mar 12, 2020 · 2 comments
Open

NodeJS location #5

remycx opened this issue Mar 12, 2020 · 2 comments

Comments

@remycx
Copy link

remycx commented Mar 12, 2020

Since Bazel is able to download its own dependencies, including JDK & NodeJS, would it be possible to automatically use the Node.JS downloaded by Bazel (when provided through the Node rules) ?

Currently having issues with no node found :

INFO: Sensor SonarTS [typescript]
ERROR: Failed to get Node.js version.No TypeScript files will be analyzed. You can exclude TypeScript files from analysis with 'sonar.exclusions' property.
java.io.IOException: Cannot run program "node": error=2, No such file or directory

The workaround defining sonar.nodejs.executable manually linked to the node install downloaded by Bazel doesn't appear to work either.

@remycx
Copy link
Author

remycx commented Mar 13, 2020

Apparently, you also have to fill in the sonar.typescript.node variable (doesn't appear on the official documentation).

I now have issues trying to make it locate the node_modules folder :/

@Zetten
Copy link
Owner

Zetten commented Mar 13, 2020

In my own project the NodeJS/TS tools are installed in the build environment, and to be honest my JS colleagues aren't really interested in the SQ side of things, so I haven't looked at it in detail yet.

I might get a chance to look at it, but if you make any progress integrating with rules_nodejs I'd be happy to take a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants