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

**URL:** <https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480>\
**Category:** SonarQube Cloud\
**Tags:** azure, bug\
**Created:** [January 17, 2024, 9:34am UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480 "2024-01-17T09:34:42Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickvol](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/patrickvol/32/48250_2.png) [@patrickvol](https://community.sonarsource.com/u/patrickvol)\
**Post date:** [January 17, 2024, 9:34am UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/1 "2024-01-17T09:34:42Z")

</div>

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/](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.

---

<div class="post-metadata">

**Author:** ![bartgommers](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/bartgommers/32/53439_2.png) [@bartgommers](https://community.sonarsource.com/u/bartgommers)\
**Post date:** [January 17, 2024, 11:33am UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/2 "2024-01-17T11:33:09Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![MarkEQ](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@MarkEQ](https://community.sonarsource.com/u/MarkEQ)\
**Post date:** [January 17, 2024, 11:42am UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/3 "2024-01-17T11:42:01Z")

</div>

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

`[INFO] SonarQube version: 8.0.0.51993`

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

`[INFO] SonarQube version: 8.0.0.52029`

---

<div class="post-metadata">

**Author:** ![faheemgani](https://avatars.discourse-cdn.com/v4/letter/f/cab0a1/32.png) [@faheemgani](https://community.sonarsource.com/u/faheemgani)\
**Post date:** [January 17, 2024, 12:06pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/4 "2024-01-17T12:06:11Z")

</div>

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:

```auto
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

```

---

<div class="post-metadata">

**Author:** ![sithmein](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sithmein/32/6598_2.png) [@sithmein](https://community.sonarsource.com/u/sithmein)\
**Post date:** [January 17, 2024, 1:58pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/5 "2024-01-17T13:58:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![AlexJulita](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@AlexJulita](https://community.sonarsource.com/u/AlexJulita)\
**Post date:** [January 17, 2024, 2:01pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/6 "2024-01-17T14:01:00Z")

</div>

Exactly the same problem here. I tried to add the sonar.javascript.exclusions=“” property as suggested in [JavaScript/TypeScript/CSS (sonarsource.com)](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/languages/javascript-typescript-css/) to skip the CSS analysis but the analysis still fails …

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [January 17, 2024, 2:02pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/7 "2024-01-17T14:02:10Z")

</div>

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.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [January 17, 2024, 2:16pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/8 "2024-01-17T14:16:04Z")

</div>

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.

&nbsp;  
Ann & the SonarCloud team

---

<div class="post-metadata">

**Author:** ![dmeneses](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dmeneses/32/2933_2.png) [@dmeneses](https://community.sonarsource.com/u/dmeneses)\
**Post date:** [January 17, 2024, 3:01pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/9 "2024-01-17T15:01:24Z")

</div>

> [@faheemgani](#):
>
> 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:
> 
> ```auto
> 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
> 
> ```

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”?

---

<div class="post-metadata">

**Author:** ![dmeneses](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dmeneses/32/2933_2.png) [@dmeneses](https://community.sonarsource.com/u/dmeneses)\
**Post date:** [January 17, 2024, 4:52pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/12 "2024-01-17T16:52:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![patrickvol](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/patrickvol/32/48250_2.png) [@patrickvol](https://community.sonarsource.com/u/patrickvol)\
**Post date:** [January 17, 2024, 5:12pm UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/14 "2024-01-17T17:12:29Z")

</div>

Yes it resolve the issue.  
Thank you for the update

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\
**Post date:** [January 26, 2024, 9:26am UTC](https://community.sonarsource.com/t/a-supported-version-of-node-js-is-required-for-running-the-analysis-of-js-ts-files/107480/17 "2024-01-26T09:26:26Z")

</div>

Closed on January 26, 2024, 9:26am UTC

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