SonarJS analysis fails due to outdated baseline-browser-mapping dependency

SonarQube Cloud
, ,
1

We are getting an error during JavaScript analysis related to an outdated baseline-browser-mapping dependency.

The analysis fails with the following message:

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

2

Hi,

As a workaround, try setting an environment variable: BROWSERSLIST_IGNORE_OLD_DATA=1 .

 
Ann

4

Hello @ldtorres,

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

We can probably move the discussion to this other topic with the exact same issue

5

Hi Ann,

Thanks for the workaround suggestion :+1:
We can confirm that setting BROWSERSLIST_IGNORE_OLD_DATA=1 avoids the analysis failure for now.

6

Hi Victor,

To clarify, this is happening in SonarCloud (not self-hosted SonarQube), during JavaScript/TypeScript analysis.

The project itself does not directly manage baseline-browser-mapping, which is why we believe this dependency is coming from the analyzer side.

Please let us know if you’d like us to move the discussion to the other referenced topic, or if you need any additional details from our side.

7

Hi @ldtorres,

i pinged you in the other post.

For future visitors, please go to NPM Sonarqube-scanner@4.3.4 error with baseline-browser-mapping