The config to share target browsers and Node.js versions between different front-end tools. It is used in:
- Autoprefixer
- Babel
- postcss-preset-env
- eslint-plugin-compat
- stylelint-no-unsupported-browser-features
- postcss-normalize
- obsolete-webpack-plugin
All tools will find target browsers automatically,
when you add the following to package.json:
"browserslist": [
"defaults and fully supports es6-module",
"maintained node versions"
]Or in .browserslistrc config:
# Browsers that we support
defaults and fully supports es6-module
maintained node versionsDevelopers set their version lists using queries like last 2 versions
to be free from updating versions manually.
Browserslist will use caniuse-lite with Can I Use data for this queries.
You can check how config works at our playground: browsersl.ist
- Tools
- Best Practices
- Queries
- Config File
- Shareable Configs
- Configuring for Different Environments
- Custom Usage Data
- JS API
- Environment Variables
- Cache
- Security Contact
- For Enterprise
Browserslist needs your support. We are accepting donations at Open Collective.
- Run
npx browserslistin your project directory to see project’s target browsers. This CLI tool is built-in and available in any project with Autoprefixer. browserslist-lintchecks your config for popular mistakes.
update-browserslist-dbis a CLI tool to update browsers DB for queries likelast 2 versionor>1%.browserslist-update-actionis a GitHub Action to automatically runupdate-browserslist-dband proposes a pull request to merge updates.
browserslist-useragent-regexpcompiles Browserslist query to a RegExp to test browser useragent.browserslist-useragent-rubyis a Ruby library to check browser by user agent string to match Browserslist.
browserslist-gaandbrowserslist-ga-exportdownload your website browsers statistics to use it in> 0.5% in my statsquery.browserslist-new-relicgenerates a custom usage data file for Browserslistbrowserslist-adobe-analyticsuses Adobe Analytics data to target browsers from your New Relic Browser data.
browserslist-rsis a Browserslist port to Rust.browserslist-browserstackruns BrowserStack tests for all browsers in Browserslist config.
These extensions will add syntax highlighting for .browserslistrc files.
-
There is a
defaultsquery, which gives a reasonable configuration for most users:"browserslist": [ "defaults" ]
-
If you want to change the default set of browsers, we recommend including
last 2 versions, not dead, > 0.2%. This is becauselast n versionson its own does not add popular old versions, while only using a percentage of usage numbers above0.2%will in the long run make popular browsers even more popular. We might run into a monopoly and stagnation situation, as we had with Internet Explorer 6. Please use this setting with caution. -
Select browsers directly (
last 2 Chrome versions) only if you are making a web app for a kiosk with one browser. There are a lot of browsers on the market. If you are making general web app you should respect browsers diversity. -
Don’t remove browsers just because you don’t know them. Opera Mini has 100 million users in Africa and it is more popular in the global market than Microsoft Edge. Chinese QQ Browsers has more market share than Firefox and desktop Safari combined.
Browserslist will use browsers and Node.js versions query from one of these sources:
.browserslistrcconfig file in current or parent directories.browserslistkey inpackage.jsonfile in current or parent directories.browserslistconfig file in current or parent directories.BROWSERSLISTenvironment variable.- If the above methods did not produce a valid result
Browserslist will use defaults:
> 0.5%, last 2 versions, Firefox ESR, not dead.
An or combiner can use the keyword or as well as ,.
last 1 version or > 1% is equal to last 1 version, > 1%.
and query combinations are also supported to perform an
intersection of all the previous queries:
last 1 version or chrome > 75 and > 1% will select
(browser last version or Chrome since 76) and more than 1% marketshare.
There are 3 different ways to combine queries as depicted below. First you start with a single query and then we combine the queries to get our final list.
Obviously you can not start with a not combiner, since there is no left-hand
side query to combine it with. The left-hand is always resolved as and
combiner even if or is used (this is an API implementation specificity).
| Query combiner type | Illustration | Example |
|---|---|---|
or/, combiner (union) |
 |
> .5% or last 2 versions > .5%, last 2 versions |
and combiner (intersection) |
 |
> .5% and last 2 versions |
not combiner (relative complement) |
 |
These three are equivalent to one another: > .5% and not last 2 versions > .5% or not last 2 versions > .5%, not last 2 versions |
A quick way to test your query is to do npx browserslist '> 0.3%, not dead'
in your terminal.
You can specify the browser and Node.js versions by queries (case insensitive):
defaults: Browserslist’s default browsers (> 0.5%, last 2 versions, Firefox ESR, not dead).- By usage statistics:
> 5%: browsers versions selected by global usage statistics.>=,<and<=work too.> 5% in US: uses USA usage statistics. It accepts two-letter country code.> 5% in alt-AS: uses Asia region usage statistics. List of all region codes can be found atcaniuse-lite/data/regions.> 5% in my stats: uses custom usage data.> 5% in browserslist-config-mycompany stats: uses custom usage data frombrowserslist-config-mycompany/browserslist-stats.json.cover 99.5%: most popular browsers that provide coverage.cover 99.5% in US: same as above, with two-letter country code.cover 99.5% in my stats: uses custom usage data.
- Last versions:
last 2 versions: the last 2 versions for each browser.last 2 Chrome versions: the last 2 versions of Chrome browser.last 2 major versionsorlast 2 iOS major versions: all minor/patch releases of last 2 major versions.
dead: browsers without official support or updates for 24 months. Right now it isIE 11,IE_Mob 11,BlackBerry 10,BlackBerry 7,Samsung 4,OperaMobile 12.1and all versions ofBaidu.- Node.js versions:
node 10andnode 10.4: selects latest Node.js10.x.xor10.4.xrelease.last 2 node versions: select 2 latest Node.js releases.last 2 node major versions: select 2 latest major-version Node.js releases.current node: Node.js version used by Browserslist right now.maintained node versions: all Node.js versions, which are still maintained by Node.js Foundation.
- Browsers versions:
iOS 7: the iOS browser version 7 directly. Note, thatop_minihas special versionall.Firefox > 20: versions of Firefox newer than 20.>=,<and<=work too. It also works with Node.js.ie 6-8: selects an inclusive range of versions.Firefox ESR: the latest Firefox Extended Support Release.PhantomJS 2.1andPhantomJS 1.9: selects Safari versions similar to PhantomJS runtime.
extends browserslist-config-mycompany: take queries frombrowserslist-config-mycompanynpm package.- By browser support:
In these example querieses6andes6-moduleare the thefeatparameter from the URL of the Can I Use page. A list of all available features can be found atcaniuse-lite/data/features.fully supports es6: browsers with full support for specific features. For example,fully supports css-gridwill omit Edge 12-15, as those browser versions are marked as having partial support.partially supports es6-moduleorsupports es6-module: browsers with full or partial support for specific features. For example,partially supports css-gridwill include Edge 12-15 support, as those browser versions are marked as having partial support.
browserslist config: the browsers defined in Browserslist config. Useful in Differential Serving to modify user’s config likebrowserslist config and fully supports es6-module.since 2015orlast 2 years: all versions released since year 2015 (alsosince 2015-03andsince 2015-03-10).unreleased versionsorunreleased Chrome versions: alpha and beta versions.not ie <= 8: exclude IE 8 and lower from previous queries.
You can add not to any query.
There is a grammar specification about the query syntax, which may be helpful if you're implementing a parser or something else.
Run npx browserslist in a project directory to see which browsers were selected
by your queries.
$ npx browserslist
and_chr 61
and_ff 56
and_qq 1.2
and_uc 11.4
android 56
baidu 7.12
bb 10
chrome 62
edge 16
firefox 56
ios_saf 11
opera 48
safari 11
samsung 5The following table maps browser names & their target devices into identifiers used by browserslist.
| Browser Name | Desktop | Android | iOS | Other Mobile |
|---|---|---|---|---|
| Android (WebView) | Android |
|||
| Baidu | Baidu |
|||
| BlackBerry | BlackBerry bb |
|||
| Chrome | Chrome |
ChromeAndroid and_chr |
↪︎ ios_saf2 |
|
| Edge | Edge |
↪︎ and_chr |
↪︎ ios_saf2 |
|
| Electron | Electron |
|||
| Firefox | Firefox ff |
FirefoxAndroid and_ff |
↪︎ ios_saf2 |
|
| Internet Explorer | Explorer ie |
ie_mob |
||
| Node.js | Node |
|||
| KaiOS Browser | kaios |
|||
| Opera | Opera |
op_mob 1 |
↪︎ ios_saf2 |
|
| Opera Mini3 | OperaMini op_mini |
|||
| QQ browser | and_qq |
|||
| Safari | Safari |
iOS ios_saf |
||
| Samsung Internet | Samsung |
|||
| UC Browser | UCAndroid and_uc |
↪︎ nameimplies that the browser uses the same engine captured byname- 1 Opera Mobile ≈ Chrome Android
- 2 All iOS browsers use WebKit
- 3 Opera Mini has 2 modes “Extreme” and “High” for data saving.
op_minitargets at the “Extreme” one. “High” is compatible with the normal Opera Mobile.
If you want to reduce config files in project root, you can specify
browsers in package.json with browserslist key:
{
"private": true,
"dependencies": {
"autoprefixer": "^6.5.4"
},
"browserslist": [
"last 1 version",
"> 1%",
"not dead"
]
}Separated Browserslist config should be named .browserslistrc
and have browsers queries split by a new line.
Each line is combined with the or combiner. Comments starts with # symbol:
# Browsers that we support
last 1 version
> 1%
not dead # no browsers without security updatesBrowserslist will check config in every directory in path.
So, if tool process app/styles/main.css, you can put config to root,
app/ or app/styles.
You can specify direct path in BROWSERSLIST_CONFIG environment variables.
You can use the following query to reference an exported Browserslist config from another package:
"browserslist": [
"extends browserslist-config-mycompany"
]For security reasons, external configuration only supports packages that have
the browserslist-config- prefix. npm scoped packages are also supported, by
naming or prefixing the module with @scope/browserslist-config, such as
@scope/browserslist-config or @scope/browserslist-config-mycompany.
If you don’t accept Browserslist queries from users, you can disable the
validation by using the or BROWSERSLIST_DANGEROUS_EXTEND environment variable.
BROWSERSLIST_DANGEROUS_EXTEND=1 npx webpackBecause this uses npm's resolution, you can also reference specific files
in a package:
"browserslist": [
"extends browserslist-config-mycompany/desktop",
"extends browserslist-config-mycompany/mobile"
]When writing a shared Browserslist package, just export an array.
browserslist-config-mycompany/index.js:
module.exports = [
'last 1 version',
'> 1%',
'not dead'
]You can also include a browserslist-stats.json file as part of your shareable
config at the root and query it using
> 5% in browserslist-config-mycompany stats. It uses the same format
as extends and the dangerousExtend property as above.
You can export configs for different environments and select environment
by BROWSERSLIST_ENV or env option in your tool:
module.exports = {
development: [
'last 1 version'
],
production: [
'last 1 version',
'> 1%',
'not dead'
]
}You can also specify different browser queries for various environments.
Browserslist will choose query according to BROWSERSLIST_ENV or NODE_ENV
variables. If none of them is declared, Browserslist will firstly look
for production queries and then use defaults.
In package.json:
"browserslist": {
"production": [
"> 1%",
"not dead"
],
"modern": [
"last 1 chrome version",
"last 1 firefox version"
],
"ssr": [
"node 12"
]
}In .browserslistrc config:
[production]
> 1%
not dead
[modern]
last 1 chrome version
last 1 firefox version
[ssr]
node 12If you have a website, you can query against the usage statistics of your site.
browserslist-ga will ask access to Google Analytics and then generate
browserslist-stats.json:
npx browserslist-ga
Or you can use browserslist-ga-export to convert Google Analytics data without giving a password for Google account.
You can generate usage statistics file by any other method. File format should be like:
{
"ie": {
"6": 0.01,
"7": 0.4,
"8": 1.5
},
"chrome": {
…
},
…
}Note that you can query against your custom usage data while also querying
against global or regional data. For example, the query
> 1% in my stats, > 5% in US, 10% is permitted.
const browserslist = require('browserslist')
// Your CSS/JS build tool code
function process (source, opts) {
const browsers = browserslist(opts.overrideBrowserslist, {
stats: opts.stats,
path: opts.file,
env: opts.env
})
// Your code to add features for selected browsers
}Queries can be a string "> 1%, not dead"
or an array ['> 1%', 'not dead'].
If a query is missing, Browserslist will look for a config file.
You can provide a path option (that can be a file) to find the config file
relatively to it.
Options:
path: file or a directory path to look for config file. Default is..env: what environment section use from config. Default isproduction.stats: custom usage statistics data.config: path to config if you want to set it manually.ignoreUnknownVersions: do not throw on direct query (likeie 12). Default isfalse.dangerousExtend: Disable security checks forextendquery. Default isfalse.throwOnMissing: throw an error if env is not found. Default isfalse.mobileToDesktop: Use desktop browsers if Can I Use doesn’t have data about this mobile version. Can I Use has only data about latest versions of mobile browsers. By default,last 2 and_ff versionsreturnsand_ff 90and with this option it returnsand_ff 91, and_ff 90. This option may lead to unknown browser version error (in example Can I Use doesn’t have data forand_ff 91yet). Default isfalse.
For non-JS environment and debug purpose you can use CLI tool:
browserslist "> 1%, not dead"You can get total users coverage for selected browsers by JS API:
browserslist.coverage(browserslist('> 1%'))
//=> 81.4browserslist.coverage(browserslist('> 1% in US'), 'US')
//=> 83.1browserslist.coverage(browserslist('> 1% in my stats'), 'my stats')
//=> 83.1browserslist.coverage(browserslist('> 1% in my stats', { stats }), stats)
//=> 82.2Or by CLI:
$ browserslist --coverage "> 1%"
These browsers account for 81.4% of all users globally$ browserslist --coverage=US "> 1% in US"
These browsers account for 83.1% of all users in the US$ browserslist --coverage "> 1% in my stats"
These browsers account for 83.1% of all users in custom statistics$ browserslist --coverage "> 1% in my stats" --stats=./stats.json
These browsers account for 83.1% of all users in custom statisticsIf a tool uses Browserslist inside, you can change the Browserslist settings with environment variables:
-
BROWSERSLISTwith browsers queries.BROWSERSLIST="> 5%" npx webpack -
BROWSERSLIST_CONFIGwith path to config file.BROWSERSLIST_CONFIG=./config/browserslist npx webpack
-
BROWSERSLIST_ENVwith environments string.BROWSERSLIST_ENV="development" npx webpack -
BROWSERSLIST_STATSwith path to the custom usage data for> 1% in my statsquery.BROWSERSLIST_STATS=./config/usage_data.json npx webpack
-
BROWSERSLIST_DISABLE_CACHEif you want to disable config reading cache.BROWSERSLIST_DISABLE_CACHE=1 npx webpack
-
BROWSERSLIST_DANGEROUS_EXTENDto disable security shareable config name check.BROWSERSLIST_DANGEROUS_EXTEND=1 npx webpack
-
BROWSERSLIST_ROOT_PATHto prevent reading files above this path.BROWSERSLIST_ROOT_PATH=. npx webpack
Browserslist caches the configuration it reads from package.json and
browserslist files, as well as knowledge about the existence of files,
for the duration of the hosting process.
To clear these caches, use:
browserslist.clearCaches()To disable the caching altogether, set the BROWSERSLIST_DISABLE_CACHE
environment variable.
To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.
Available as part of the Tidelift Subscription.
The maintainers of browserslist and thousands of other packages are working
with Tidelift to deliver commercial support and maintenance for the open source
dependencies you use to build your applications. Save time, reduce risk,
and improve code health, while paying the maintainers of the exact dependencies
you use. Learn more.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent