A supported version of Node.js is required for running the analysis of JS/TS files

We have a CICD pipeline in Azure what always works with SonarCloud connection.
But, today we get the following error without changing the code:

Error while running Node.js. A supported version of Node.js is required for running the analysis of JS/TS files. Please make sure a supported version of Node.js is available in the PATH. Alternatively, you can exclude JS/TS files from your analysis using the ‘sonar.exclusions’ configuration property. See the docs for configuring the analysis environment: https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/languages/javascript-typescript-css/

Is there an update what we need to do? Or is there a bug in the connection?
Thanks for helping.

1 Like

We’re experiencing the same issue. Looks like sonar pushed a breaking update. Can this be reverted/fixed please?

We are also experiencing this problem since this morning, we found the following line in the most recent succesful build:

[INFO] SonarQube version:

And the first failed build without any changes to our code shows this:

[INFO] SonarQube version:

1 Like

We are having the same issue with this, nothing has changed in the Dockerfile but all of our builds are failing:

Caused by: org.sonar.plugins.javascript.nodejs.NodeCommandException: Error when running: 'node -v'. Is Node.js available during analysis?

Running node -v before doing the sonar analysis returns a node version:

2024-01-17T12:00:16.9876517Z Step 30/77 : RUN node -v
2024-01-17T12:00:18.6495389Z  ---> Running in 8324a1a3c308
2024-01-17T12:00:19.0718650Z v18.18.2

We don’t have node installed and have been getting the error message since always. However it never failed the analysis until today. Now the analysis fails and hence all builds fail.

Exactly the same problem here. I tried to add the sonar.javascript.exclusions=“” property as suggested in JavaScript/TypeScript/CSS (sonarsource.com) to skip the CSS analysis but the analysis still fails …

Hi all,

Thanks for the reports. We’re currently investigating and will update here when we know more.

Feel free to add additional specifics here if they’re not already represented in the thread.


Hi again,

We’re reverting a change that was deployed at 10:00 CEST today. We expect deployment to be complete in ~2h.

We apologize for the inconvenience.

Ann & the SonarCloud team

Could you please check if you had any warnings regarding missing node before it started failing today? Warnings like “JavaScript/TypeScript/CSS rules were not executed”?

We’ve reverted a change that caused the scanner to fail when nodejs is not found.

Please let us know if that resolves the issue.

Yes it resolve the issue.
Thank you for the update

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.