browserslist / browserslist

🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env

Home Page:https://browsersl.ist

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[feature request] add audience coverage for implicitly covered browsers

MonstraG opened this issue · comments

Query

"browserslist": [
  "defaults and fully supports es6-module",
  "maintained node versions"
]

Gives:
Audience coverage: 88.6 %
And among other browsers,

Firefox 122 - 0.28%
Firefox 121 - 1.3%
Firefox 115 - 0.47%

But Firefoxes 116-120 are not included because they are not covered by defaults.
But at the same time, if I'm targeting 116, great majority of the all never versions are supported also. (I would be interested to know when they are not btw)

If I add all minimal versions I cover:

defaults and fully supports es6-module,
maintained node versions,
safari >= 16.6
ios >= 15.6
chrome >= 109
firefox >=115

Then audience coverage jumps up:
Audience coverage: 92.0 %

So, most of the time, in reality I support 92% of the browsers, but tool reports 88.6% in practice.

Adding this "in practice" number I would think would be helpful:
image
With maybe a tooltip of 92 how was achieved.

if I'm targeting 116, great majority of the all never versions are supported also

It is true only in a majority of the cases, but not for all of them.

We have rare examples of features which was supported only inside some versions range (because they were deprecated later).

Firefox 115 is very specific ESR version. I am not sure that it is safe to say that 116 is similar to 115.

I am aware of that in general, but cannot recall any recent examples.