NPM Sonarqube-scanner@4.3.4 error with baseline-browser-mapping

SonarQube Server / Community Build
1

Throws the same error as already know with Azure DevOps scanner. This breaks the CI/CD pipeline.

[DBG] 03:25:15.773 INFO Using embedded Node.js runtime.
04:25:15 [DBG] 03:25:15.774 INFO Using Node.js executable: ‘/root/.sonar/js/node-runtime/node’.
04:25:16 03:25:16.922 ERROR [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D
04:25:16 [ERR] 03:25:16.922 ERROR [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D
04:25:17 [DBG] 03:25:17.071 INFO Memory configuration: OS (29365 MB), Node.js (4288 MB).
04:25:17 [DBG] 03:25:17.143 INFO WebSocket client connected on /ws
04:25:17 [DBG] 03:25:17.144 INFO Plugin version: [11.7.1.36988]
04:25:18 03:25:18.177 ERROR [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D

1 Like
SonarJS analysis fails due to outdated baseline-browser-mapping dependency
SonarJS analysis fails due to outdated baseline-browser-mapping dependency
Sonar Community Roundup; Jan 24 - 30, 2026
2

Hi,

I need to ask the dumb question: what if you run the update?

 
Thx,
Ann

3

Hi,
What you mean with update and what to update?

I use the newest sonar scanner npm package and the newest sonar-scanner-cli.

I don’t see a place where I could update anything

I use plain sonar scan with NPM and sonar-scanner-cli.

Thx
Jörg

4

Hi Joerg,

I meant this update:

You can also set an environment variable: BROWSERSLIST_IGNORE_OLD_DATA=1 and the error should go away.

 
Ann

6

Hello @JW26,

What version of SonarQube are you using? We are aware of this happening in the past, but was (in principle) fixed 4 years ago

7

Hi Victor,
We use v2025.6.1 (117629) Developer Edition

I never saw this error message before.

8

Hi Ann,
I installed the package you proposed, but nothing changed it seems there is no way to solve the issue from outside of sonar qube.

Jörg

9

Hello @JW26 @ldtorres ,

yes indeed this is a transitive dependency of our analyzer. As I mentioned, we spotted these errors some years ago coming from this file. We fixed it by providing the environment variable BROWSERSLIST_IGNORE_OLD_DATA=true=true in the analyzer.

To investigate further could you please share the full debug logs, please?

Cheers

10

We now understand the issue.

SonarCloud should already be fixed and the analysis should succeed.

For self-hosted users, these versions are affected:

Community Edition:

  • 25.12.0
  • 26.1.0

Server/Developer/Enterprise:

  • 2025.6.0
  • 2025.6.1

the analysis itself is not failing, but the error logs may make your CI pipeline fail. The upcoming SQ release will contain a fixed version of SonarJS.

Sorry for the inconvenience.

1 Like
11

Hi Victor,
Thanks for the investigation and the solution.

Jörg

2 Likes