ERROR: Browserslist: caniuse-lite is outdated

In the scanner logs we can see:

build	13-Sep-2021 11:13:40	INFO: Analyzing 42 files using tsconfig:...
error	13-Sep-2021 11:13:47	ERROR: Browserslist: caniuse-lite is outdated. Please run:
error	13-Sep-2021 11:13:47	ERROR: npx browserslist@latest --update-db
error	13-Sep-2021 11:13:47	ERROR: 
error	13-Sep-2021 11:13:47	ERROR: Why you should do it regularly:
error	13-Sep-2021 11:13:47	ERROR:
[here missing further lines for the scanned module]

Scanner version:

That does not impact the scan or build it seems, but still might be good to fix.

We are seeing the same errors/messages. No impact on scan. We are using the latest LTS Developer docker image without any further modifications or plugins.

We are having same exact issue and it’s impacting our ci/cd builds using JavaScript , we have an Enterprise Edition Licence (Version 8.9.1 (build 44547) , we are using SonarScanner.MSBuild.exe wrapped in an custom application. The ERRORS flagged we think that must be flagged as Warnings, cause the Analysis complete successful.Nothing has changed in our side, no versions, no updates, so no idea from where this error is coming … can you give us a hint where to look or how to solve it?

SonarScanner for MSBuild 5.3.1
Using the .NET Framework version of the Scanner for MSBuild
Post-processing started.

INFO: SonarScanner

ERROR: Browserslist: caniuse-lite is outdated. Please run:
ERROR: npx browserslist@latest --update-db

INFO: 3/3 source files have been analyzed
INFO: Sensor JavaScript analysis [javascript] (done) | time=13702ms
INFO: Sensor TypeScript analysis [javascript]
INFO: No input files found for analysis

INFO: The SonarScanner CLI has finished

1 Like

I believe it’s not “impacting” the builds, as your scan completes successfully.

It’s just an error in the logs and probably some other side-effects like not properly analysing all the “current” rules that would come with the new version of the browserslist package.

Still, would be good to have a new patch release with the updated version of the package.


indeed there is this automatic update mechanism in browserlist dependency. I created two tickets to handle this issue

1 Like

I’ve just found that the message can be suppressed by setting environment variable BROWSERSLIST_IGNORE_OLD_DATA=true

I found this in

It seems to fix the problem for me.Can you test on your setup?