
Security News
OWASP 2025 Top 10 Adds Software Supply Chain Failures, Ranked Top Community Concern
OWASP’s 2025 Top 10 introduces Software Supply Chain Failures as a new category, reflecting rising concern over dependency and build system risks.
eslint-plugin-compat
Advanced tools
Lint the browser compatibility of your code

npm install eslint-plugin-compat
eslint.config.mjs)import compat from "eslint-plugin-compat";
export default [compat.configs["flat/recommended"]];
.eslintrc.json){
"plugins": ["compat"],
"extends": ["plugin:compat/recommended"],
"env": {
"browser": true,
},
// ...
}
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.
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",
],
},
}
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,
},
}
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",
},
},
}
For a minimal demo, see amilajack/eslint-plugin-compat-demo
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.
This project exists thanks to all the people who contribute. [Contribute].
Become a financial contributor and help us sustain our community. [Contribute]
Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]
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.
FAQs
Lint browser compatibility of API used
The npm package eslint-plugin-compat receives a total of 708,536 weekly downloads. As such, eslint-plugin-compat popularity was classified as popular.
We found that eslint-plugin-compat demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
OWASP’s 2025 Top 10 introduces Software Supply Chain Failures as a new category, reflecting rising concern over dependency and build system risks.

Research
/Security News
Socket researchers discovered nine malicious NuGet packages that use time-delayed payloads to crash applications and corrupt industrial control systems.

Security News
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.