browserslist

Browserslist

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 versions

Developers 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

  

Docs

Read full docs here.

Similar packages

Other packages similar to browserslist

caniuse-api

The caniuse-api provides raw browser support data from Can I Use, which is similar to the data that browserslist uses. However, it focuses more on querying specific features for browser support rather than defining a list of supported browsers for a project.

autoprefixer

Autoprefixer is a CSS post-processor that uses browserslist to add vendor prefixes to CSS rules. It is a consumer of browserslist data rather than a direct alternative, but it serves a similar purpose in terms of browser compatibility.

@babel/preset-env

Babel's preset-env is a smart preset that allows you to use the latest JavaScript without needing to micromanage which syntax transforms are needed by your target environment. It uses browserslist to determine which features need to be transformed or polyfilled. While not a direct alternative, it shares the goal of adapting code to be compatible with different environments.