Conversation
No, you can call |
README.md
Outdated
| * `cover 99.5% in US`: same as above, with [two-letter country code]. | ||
| * `cover 99.5% in my stats`: uses [custom usage data]. | ||
| * `cover 99.5% in browserslist-config-mycompany stats`: uses [custom usage data] from `browserslist-config-mycompany/browserslist-stats.json`. | ||
| * By [Baseline](https://web-platform-dx.github.io/web-features) feature support using [`baseline-browser-mapping`](https://github.com/web-platform-dx/baseline-browser-mapping) |
There was a problem hiding this comment.
We don’t mention data sources in other queries (like node or chromium). Do you have reason to do it here?
There was a problem hiding this comment.
Can drop it if you prefer, I thought it might reduce the number of issues people create on browserslist when really they have an issue with baseline-browser-mapping ;-)
There was a problem hiding this comment.
Bumping this, happy to remove it if you'd prefer it not be there, but can leave it in if you agree that it might reduce the potential for mis-filed issues if devs know where the data is coming from.
Co-authored-by: Andrey Sitnik <[email protected]>
|
Hey @ai Various changes made here including:
I'm good to change this to Ready for review if you are, although I still don't know if the way I've composed the grammar is correct. LMK how you'd like to proceed. |
|
Sorry, I lost myself in my new open source to prevent supply chain attack. I will review updates during this week. |
|
@ai FYI, I've just updated |
|
Thanks for waiting. Baseline queries was released in 4.26.0. |
|
I will update https://browsersl.ist and promote in socials a little later. I need to fix something on website. |
|
BTW, Baseline queries already on website (but I need to write docs) 
|
|
@tonypconway I cleaned up docs a little and write special version for website. Can you check please as native English speaker:
If everything is OK, I will announce it on social media next week. |
|
Hey @ai thanks for these My only nitpick is the wording for * `baseline widely available`: browser versions that support all [Baseline Widely available](https://webstatus.dev/?q=baseline_status%3Awidely) features which have been interoperable in the Baseline core browser set for at least 30 months.
* `baseline newly available`: browser versions that support all [Baseline Newly available](https://webstatus.dev/?q=baseline_status%3Anewly) features which are interoperable in the Baseline core browser set today.I know it's a bit wordy, but I'd rather it be accurate and avoid any confusion. Likewise, I'm keen to be clear on what we're returning, so people don't wonder why they're seeing releases from before the 30 months cut off date. [baseline widely available](https://browsersl.ist/#q=baseline+widely+available) versions of Chrome, Edge, Firefox, and Safari supports the current [Baseline Widely available](https://webstatus.dev/?q=baseline_status%3Anewly) set of features, which have been interoperable in those browsers for at least 30 months.
[baseline newly available](https://browsersl.ist/#q=baseline+newly+available) recent versions of Chrome, Edge, Firefox, and Safari, which supports the current [Baseline Newly available](https://webstatus.dev/?q=baseline_status%3Anewly) set of features, which are interoperable in those browsers today.My other question would be whether it's worth hoisting the
KaiOS 4.0 is the only version compatible with Widely. If you try, e.g. |
|
Thanks. I fixed the text and will announce changes tomorrow.
пн, 15 сент. 2025 г. в 17:43, Tony Conway ***@***.***>:
… *tonypconway* left a comment (browserslist/browserslist#903)
<#903 (comment)>
Hey @ai <https://github.com/ai> thanks for these
1. repo docs:
https://github.com/browserslist/browserslist?tab=readme-ov-file#full-list
My only nitpick is the wording for widely available and newly available -
it's not "all versions from the last 30 months" or "latest" versions. It's
sometimes the case that Widely and Newly will include 2 or 3 versions of
some subset of the browsers before the cut off date because they already
supported all the features that were WA on that date. Could we change to:
* `baseline widely available`: browser versions that support all [Baseline Widely available](https://webstatus.dev/?q=baseline_status%3Awidely) features which have been interoperable in the Baseline core browser set for at least 30 months.
* `baseline newly available`: browser versions that support all [Baseline Newly available](https://webstatus.dev/?q=baseline_status%3Anewly) features which are interoperable in the Baseline core browser set today.
I know it's a bit wordy, but I'd rather it be accurate and avoid any
confusion.
2. website https://browsersl.ist/
Likewise, I'm keen to be clear on what we're returning, so people don't
wonder why they're seeing releases from before the 30 months cut off date.
[baseline widely available](https://browsersl.ist/#q=baseline+widely+available) versions of Chrome, Edge, Firefox, and Safari supports the current [Baseline Widely available](https://webstatus.dev/?q=baseline_status%3Anewly) set of features, which have been interoperable in those browsers for at least 30 months.[baseline newly available](https://browsersl.ist/#q=baseline+newly+available) recent versions of Chrome, Edge, Firefox, and Safari, which supports the current [Baseline Newly available](https://webstatus.dev/?q=baseline_status%3Anewly) set of features, which are interoperable in those browsers today.
My other question would be whether it's worth hoisting the with downstream
out of the advanced section? I know you were keen to make sure those
browser versions weren't excluded.
3. Also for some reason I don’t see KaiOS on website on query with
kaios.
https://browsersl.ist/#q=baseline+widely+available+with+downstream+including+kaios
Can I ask you to double-check the code?
KaiOS 4.0 is the only version compatible with Widely. If you try, e.g.baseline
2020 with downstream including kaios you'll see the 3.0 range in there
because it uses Gecko 123. 4.0 isn't currently in caniuse-db, but it's
something I'm discussing with @Fyrd <https://github.com/Fyrd>.
—
Reply to this email directly, view it on GitHub
<#903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAEXDZILKTH2VQNTACOQVD3S3NDVAVCNFSM6AAAAACFQ5Y6YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOJSHAZTANZRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Carpe diem.
|
With the release of browserslist v4.24.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.24.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.24.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.24.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.24.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.26.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.26.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.26.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
With the release of browserslist v4.26.0, the 'baseline' query is now natively supported. This removes the need for a custom tool to generate the browserslist configuration. See: browserslist/browserslist#903
|
Using this at work in production and on a personal project about to be in production, super useful! Thank you for implementing this :) |
3 participants
This PR fixes #771 by adding support for Baseline queries. Supported query types are as follows:
baseline newly availableorbaseline widely availableto get all browser versions that support the stated Baseline feature set.baseline 20XXto get browser versions that support all newly available features at the end of the stated year.baseline widely available on YYYY-MM-DD… with downstreamincludes browsers outside the Baseline core browser set where compatibility can be inferred by Chromium/Gecko version… including kaiosincludes KaiOS based on Gecko version mapping. KaiOS requires an extra step because it is a substantially different interface paradigm to other browsers and we need to make sure developers are including it consciously.The above queries use
baseline-browser-mappingas a dependency, and consequently the size limit ofbrowserslistis increased to 30kB. It also adds tests for the Baseline queries.