You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# <imgsrc="https://unpkg.com/[email protected]/assets/icon.svg"height="25"alt="Baseline Widely Available logo"> browserslist-config-baseline
2
2
3
-
[Browserslist][1] config based on [WebDX Baseline][2] (as seen on MDN).
3
+
A [browserslist](https://www.npmjs.com/package/browserslist) config based on [Web Platform Baseline](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility).
4
4
5
-
Baseline identifies web platform features that work across browsers. Baseline
6
-
helps you decide when to use a feature by telling you when it is less likely to
7
-
cause compatibility problems for your site's visitors.
5
+
Baseline identifies web platform features that work across browsers. Baseline helps you decide when to use a feature by telling you when it is less likely to cause compatibility problems for your site's visitors. There are two ways of targeting a Baseline feature set:
1.[Baseline Widely Available](#baseline-widely-available) - includes all features that were fully supported in Chrome, Edge, Firefox and Safari **30 months before the current data**.
8
+
2.[Baseline year feature sets](#baseline-year-feature-sets) - includes all features that were fully supported in Chrome, Edge, Firefox and Safari **at the end of a given calendar year**.
9
+
10
+
You should check your analytics to see which browser versions are prevalent in your userbase before selecting a Baseline target.
11
+
12
+
## Baseline Widely Available
11
13
12
14
<!-- prettier-ignore -->
13
15
```json
@@ -18,21 +20,78 @@ cause compatibility problems for your site's visitors.
18
20
}
19
21
```
20
22
21
-
## Browsers
23
+
> **WARNING:**
24
+
> The default configuration of this module approximates Baseline Widely Available by taking all versions of the core browser set released in the last 2.5 years. However, there will be discrepancies between the real Baseline Widely Available feature set and the minimum browser versions this module returns. The real Baseline Widely Available feature set is supported by one or more versions of the core browser set prior to the 2.5 year cut off. As a result, this module may cause your packager to skip polyfills that you need or fail to highlight improper usage of newer web features. To provide a fully accurate list of browsers compatible with Baseline Widely Available, consider using [`bl2bl`](https://npmjs.org/bl2bl).
25
+
26
+
## Baseline year feature sets
22
27
23
-
This config includes versions of
28
+
Baseline year feature sets include all the web platform features that were fully supported in the core browser set at the end of a given calendar year. To use a Baseline year feature set, add the year in the format `/YYYY` to the end of your `extends` statement:
29
+
30
+
<!-- prettier-ignore -->
31
+
```json
32
+
{
33
+
"browserslist": [
34
+
"extends browserslist-config-baseline/2020"
35
+
]
36
+
}
37
+
```
38
+
39
+
This equates to the following `browserslist` config:
40
+
41
+
```json
42
+
{
43
+
"browserslist": [
44
+
"Chrome >= 87",
45
+
"ChromeAndroid >= 87",
46
+
"Edge >= 87",
47
+
"Firefox >= 83",
48
+
"FirefoxAndroid >= 83",
49
+
"Safari >= 14",
50
+
"iOS >= 14"
51
+
]
52
+
}
53
+
```
24
54
25
-
- Apple Safari (iOS)
26
-
- Apple Safari (macOS)
27
-
- Google Chrome (Android)
28
-
- Google Chrome (desktop)
29
-
- Microsoft Edge (desktop)
30
-
- Mozilla Firefox (Android)
31
-
- Mozilla Firefox (desktop)
55
+
The minimum browser versions that support these feature sets are usually the last version released in that year or a few versions earlier. The feature set > browser version mappings in this module were determined using [`baseline-browser-mapping`](https://npmjs.org/baseline-browser-mapping).
56
+
57
+
## Include Chromium downstream browsers
58
+
59
+
To include browsers that implement Chromium where possible, insert `/with-downstream` into your statement between the root directory and the year:
This equates to the following `browserslist` config:
71
+
72
+
```json
73
+
{
74
+
"browserslist": [
75
+
"Chrome >= 87",
76
+
"ChromeAndroid >= 87",
77
+
"Edge >= 87",
78
+
"Firefox >= 83",
79
+
"FirefoxAndroid >= 83",
80
+
"Safari >= 14",
81
+
"iOS >= 14",
82
+
"Opera >= 73",
83
+
"op_mob >= 62",
84
+
"Samsung >= 14.0",
85
+
"Android >= 87",
86
+
"and_uc >= 15.3",
87
+
"and_qq >= 11.7"
88
+
]
89
+
}
90
+
```
32
91
33
-
released within the last 30 months. This means that all features tagged as
34
-
**widely available** on MDN should be safe to use without any polyfills.
92
+
The minimum browser versions of non-core browsers are provided by `baseline-browser-mapping` based on two sources: [`@mdn/browser-compat-data`](https://npmjs.org/@mdn/browsers-compat-data) where those engine version mappings exist, and parsed user agents from [`useragents.io`](https://useragents.io) where necessary. For more information on these mappings, please see [`baseline-browser-mapping`'s README](https://www.npmjs.com/package/baseline-browser-mapping#downstream-browsers).
35
93
36
94
## See also
37
95
96
+
-[bl2bl](https://github.com/web-platform-dx/bl2bl) - a command line tool for generating Baseline compliant `browserslist` configurations that are readable in `package.json` and/or `.browserslistrc` files.
0 commit comments