eslint-plugin-compat

What is eslint-plugin-compat?

eslint-plugin-compat is an ESLint plugin that helps developers ensure their code is compatible with specified browser versions. It checks for the use of modern JavaScript features and APIs that may not be supported in older browsers, helping to avoid runtime errors in production.

What are eslint-plugin-compat's main functionalities?

Check browser compatibility

This configuration extends the recommended settings for eslint-plugin-compat and sets the environment to browser. It also specifies polyfills for 'fetch' and 'Promise' to ensure compatibility with older browsers.

module.exports = {
  "extends": [
    "plugin:compat/recommended"
  ],
  "env": {
    "browser": true
  },
  "settings": {
    "polyfills": [
      "fetch",
      "Promise"
    ]
  }
};

Custom browser targets

This configuration allows you to specify custom browser targets using the 'browsers' setting. In this example, it targets the last 2 versions of all browsers and browsers with more than 1% market share.

module.exports = {
  "extends": [
    "plugin:compat/recommended"
  ],
  "env": {
    "browser": true
  },
  "settings": {
    "browsers": [
      "last 2 versions",
      "> 1%"
    ]
  }
};

Other packages similar to eslint-plugin-compat

eslint-plugin-es

eslint-plugin-es is an ESLint plugin that checks for ECMAScript (JavaScript) version compatibility. It ensures that your code does not use features from newer ECMAScript versions that are not supported in your target environments. While it focuses on ECMAScript versions, it can complement eslint-plugin-compat for broader compatibility checks.

README

eslint-plugin-compat

Lint the browser compatibility of your code

Setup

1. Install

npm install eslint-plugin-compat

2. Update ESLint Config

New Config (eslint.config.mjs)

import compat from "eslint-plugin-compat"

export default [
  compat.configs['flat/recommended']
];

Legacy Config (.eslintrc.json)

{
  "plugins": ["compat"],
  "extends": ["plugin:compat/recommended"],
  "env": {
    "browser": true
  }
  // ...
}

3. Configure Target Browsers

Browser targets are configured using browserslist. You can configure browser targets in your package.json:

package.json

{
  // ...
  "browserslist": ["defaults"]
}

If no configuration is found, browserslist defaults to "> 0.5%, last 2 versions, Firefox ESR, not dead".

See browserslist/browserslist for more details.

Adding Polyfills

Add polyfills to the settings section of your eslint config. Append the name of the object and the property if one exists. Here are some examples:

{
  // ...
  "settings": {
    "polyfills": [
      // Example of marking entire API and all methods and properties as polyfilled
      "Promise",
      // Example of marking specific method of an API as polyfilled
      "WebAssembly.compile",
      // Example of API with no property (i.e. a function)
      "fetch",
      // Example of instance method, must add `.prototype.`
      "Array.prototype.push"
    ]
  }
}

Linting ES APIs (Experimental)

This plugin also supports linting the compatibility of ES APIs in addition to Web APIs. This is an experimental feature and is disabled by default. To enable this feature, add the following to your eslint config:

{
  // ...
  "settings": {
    "lintAllEsApis": true
  }
}

Configuring for Different Environments

Browserslist allows specifying different browser queries for multiple environments. By default, this plugin targets the production browserslist environment. To change this default, set the settings.browserslistOpts.env property in your eslint config:

Example:

A browserslist with multiple environments:

  "browserslist": {
    "production": [
      "> 1%",
      "not dead"
    ],
    "modern": [
      "last 1 chrome version",
      "last 1 firefox version"
    ]
  }

Target modern browserslist environment:

{
  "settings": {
    "browserslistOpts": {
      "env": "modern"
    }
  }
}

Demo

For a minimal demo, see amilajack/eslint-plugin-compat-demo

Inspiration

Toolchains for native platforms, like iOS and Android, have had API linting from the start. It's about time that the web had similar tooling.

This project was inspired by a two hour conversation I had with someone on the experience of web development and if it is terrible or not. The premise they argued was that x browser doesn't support y feature while z browser does. Eventually, I agreed with him on this and made this plugin to save web developers from having to memorize the browser compatibility of WebAPIs.

Related

• ast-metadata-inferer
• compat-db

Contributors

Code Contributors

This project exists thanks to all the people who contribute. [Contribute].

Financial Contributors

Become a financial contributor and help us sustain our community. [Contribute]

Individuals

Organizations

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]