# ERROR: Only Node.js v14.17 or later is supported, got 10.24.1

**URL:** <https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026>\
**Category:** SonarQube Server / Community Build\
**Tags:** azuredevops, dotnet\
**Created:** [June 5, 2023, 9:24pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026 "2023-06-05T21:24:43Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![tcochran](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tcochran](https://community.sonarsource.com/u/tcochran)\
**Post date:** [June 5, 2023, 9:24pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/1 "2023-06-05T21:24:43Z")

</div>

- which versions are you using: sonar-scanner-msbuild 5.13.0, Sonarqube 9.9 LTS
- how is SonarQube deployed: Docker
- what are you trying to achieve: Trying to exclude node.js versions from being scanned in our Azure DevOps pipeline using Sonarqube Azure DevOps extension.
- what have you tried so far to achieve this: We set in the “Prepare for sonarqube analysis” step under Advanced `sonar.exclusions=/*.js,/*.ts`

In our Azure DevOps build pipeline, we have a node.js tool installer task which is set to 10.x so it currently installs 10.24.1. We also have sonarqube tasks and have `sonar.exclusions=/*.js,/*.ts` set in the “Prepare for sonarqube analysis” task but when the “Run Code analysis” task comes around it ends up producing an error stating

> Only Node.js v14.17 or later is supported, got 10.24.1.

Its like our sonar.exclusions setting is not working. Anyway, to fix this in our Azure DevOps pipeline?

---

<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:** [June 6, 2023, 2:06pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/2 "2023-06-06T14:06:56Z")

</div>

Hi,

I believe Node.js is also used in the analysis of CSS. Try excluding it as well.

&nbsp;  
HTH,  
Ann

---

<div class="post-metadata">

**Author:** ![tcochran](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tcochran](https://community.sonarsource.com/u/tcochran)\
**Post date:** [June 6, 2023, 2:20pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/3 "2023-06-06T14:20:21Z")

</div>

Will try that. Thanks.

---

<div class="post-metadata">

**Author:** ![tcochran](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tcochran](https://community.sonarsource.com/u/tcochran)\
**Post date:** [June 6, 2023, 4:12pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/4 "2023-06-06T16:12:18Z")

</div>

> [@ganncamp](#):
>
> Node.js is also used in the analysis of CSS.

Edited sonar.exclusions to be `sonar.exclusions=/*.js,/*.ts,/*.css` but the build still gave me “ERROR: Only Node.js v14.17 or later is supported, got 10.24.1.”

---

<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:** [June 6, 2023, 5:40pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/5 "2023-06-06T17:40:46Z")

</div>

Hi,

Can you provide the full analysis log, please?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

[This guide](https://community.sonarsource.com/t/how-to-find-logs-about-importing-code-coverage/73317) will help you find them.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![tcochran](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tcochran](https://community.sonarsource.com/u/tcochran)\
**Post date:** [June 6, 2023, 6:20pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/6 "2023-06-06T18:20:58Z")

</div>

Full analysis log from Azure DevOps pipeline:

[analysis log.txt](https://community.sonarsource.com/uploads/short-url/ndMD5Nh2zbWFJ4Got6fCzbzwM2v.txt) (90.5 KB)

---

<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:** [June 6, 2023, 6:32pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/7 "2023-06-06T18:32:03Z")

</div>

Hi,

I see from your log that analysis succeeds. So I guess you’re just trying to get a “clean” analysis?

I’ll be honest, and say I didn’t pay too much attention to the exclusions you quoted in your OP. But going back to them now - or rather, now that I’ve seen them in your analysis log:

> `2023-06-06T15:40:08.2672592Z INFO: Excluded sources: **/bootstrap.css,** /Bootstrap.cs, **/bootstrap.js,** /bootstrap*.js, **/jquery*.js,** /jquery.js, **/*.xsd,** /modernizr*.js, font-awesome.css, /*.js, /*.ts, /*.css`

I can say you want to adjust them some. Per [the docs](https://docs.sonarqube.org/latest/project-administration/narrowing-the-focus/#wildcard-patterns)

> - `*` Match zero or more characters (not including the directory delimiter, `/`).
> - `**` Match zero or more directory segments within the path.
> - `?` Match a single character (not including the directory delimiter, `/`).

So that means you need this:

` **/bootstrap.css,** /Bootstrap.cs, **/bootstrap.js,** /bootstrap*.js, **/jquery*.js,** /jquery.js, **/*.xsd,** /modernizr*.js, **/font-awesome.css,** /*.js, **/*.ts,** /*.css`

&nbsp;  
HTH,  
Ann

---

<div class="post-metadata">

**Author:** ![tcochran](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tcochran](https://community.sonarsource.com/u/tcochran)\
**Post date:** [June 6, 2023, 8:34pm UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/8 "2023-06-06T20:34:52Z")

</div>

> [@ganncamp](#):
>
> \*\*/bootstrap.css, \*\*/Bootstrap.cs, \*\*/bootstrap.js, \*_/bootstrap_.js, \*_/jquery_.js, \*\*/jquery.js, \*\*/_.xsd, \*/modernizr.js, \*\*/font-awesome.css, \*\*/_.js, \*\*/_.ts, \*\*/_.css

Tried including this in sonar.exclusions but got the same error.

[analysis log.txt](https://community.sonarsource.com/uploads/short-url/lwLw3swKsThyTmQSm9OnAujXPNT.txt) (90.9 KB)

---

<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:** [June 7, 2023, 11:32am UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/9 "2023-06-07T11:32:41Z")

</div>

Hi,

This is happening in the CSS sensor. I guess it’s checking (or trying to) for CSS in other file types. Since you probably don’t want to exclude those other file types from analysis, the options are to ignore this error or upgrade Node.js.

&nbsp;  
🤷‍♀️  
Ann

---

<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:** [June 14, 2023, 11:32am UTC](https://community.sonarsource.com/t/error-only-node-js-v14-17-or-later-is-supported-got-10-24-1/92026/10 "2023-06-14T11:32:45Z")

</div>

Closed on June 14, 2023, 11:32am UTC

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