amilajack/eslint-plugin-compat

Check the browser compatibility of your code

View on GitHub ↗Jump to charts ↓

amilajack/eslint-plugin-compat has 3k+ stars and 100+ forks on GitHub, is written in TypeScript, and was last pushed on Jul 23, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on September 30th, 2016
Open Issues & Pull Requests: 83 (+0)
GitHub issues: Enabled
Number of forks: 116
Total Stargazers: 3,183 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.8 days
Mean response time: 171.3 days
90th percentile: 387.5 days
Tracked items: 20

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 621 days
Stale 30+ days: 18
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • released (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

eslint-plugin-compat is an ESLint plugin that checks whether the APIs and language features used in your code are supported by your target browsers.

The plugin solves the problem of accidentally using browser APIs or JavaScript features that are not available in browsers you need to support. It works by analyzing your code against a browserslist configuration to determine which browsers you target, then checking each API call and language feature against compatibility data to flag unsupported usage. This catches compatibility issues at lint time rather than discovering them through testing or user reports.

You should adopt this tool if you maintain a codebase that must run on specific older or less-capable browsers. It works well for projects where you have defined browser support requirements through a browserslist configuration. The plugin integrates directly into your ESLint workflow, making compatibility checks part of your standard linting process without requiring additional tooling.

The project shows consistent maintenance with regular updates to address issues and incorporate feedback. Pull requests receive timely review and merging. The codebase demonstrates active development focused on improving detection accuracy and expanding API coverage. Issue responses indicate engagement with user-reported problems and feature requests.