eslint-plugin-compat
browserslist
| eslint-plugin-compat | browserslist | |
|---|---|---|
| 7 | 57 | |
| 3,126 | 13,306 | |
| 0.1% | 0.4% | |
| 5.8 | 7.9 | |
| 6 months ago | 24 days ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
eslint-plugin-compat
-
Is there an open source tool for analyzing JS/CSS compatibility with different browsers?
I've looked for this in the past. There's not much for this that is totally comprehensive. You might find success with eslint-plugin-compat which will error when using things that aren't supported in your browsers.
- Comparing Babel, Sucrase, and Similar Libraries
- Is there a plugin (for Jetbrains IDEs) to check javascript code compatibility for certain browser versions?
- Question about minimum browser compatibility
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature.
[0] https://github.com/amilajack/eslint-plugin-compat
- Facts every web dev should know before they burn out and turn to painting
-
[AskJS] Best practices for polyfills in libraries?
For now I'm trying to set up [eslint-plugin-compat](https://github.com/amilajack/eslint-plugin-compat) to check it for me, but I'm not sure it works — get 0 errors and 3 polyfills for a test snippet.
browserslist
-
Supporting ancient browsers using modern Web-Tooling
This plugin automatically converts modern JavaScript and adds necessary polyfills based on Browserlist-targets using Babel.
-
Why and How to Migrate Your React App from CRA to Vite
For a production build, you are likely using Browserslist, by default Vite targets browsers that support native ES Modules, native ESM dynamic import, and import.meta.
- Browserslist/browserslist: `not and_UC all`
-
Shoelace: A forward-thinking library of web components
Not these days, where most people are using evergreen browsers and iOS users upgrade very quickly.
Take a look at the defaults for browserslist, for example:
https://browsersl.ist/#q=defaults
It just barely supports Safari 15, on iOS only, and that’s likely to go away imminently because it’s under 1% usage.
-
How to Clone an Object in JavaScript
browserslist
-
How we improved page load speed for Next.js ecommerce website by 1.5 times
We compile JS only for modern browsers. The list of default browsers in Next can be overridden in your browserslist.
-
The Need for Speed: Next.js Performance Overhaul with Polyfills and SWC
In the latest versions of Next.js, targeting specific browsers or features is a breeze using the Browserslist configuration in your package.json file. The latest version of Next.js (v13) uses the following configuration by default:
-
How can I find out if I should support IE 9/10/11?
For a more general answer to browser support, check out https://github.com/browserslist/browserslist. That seems to be standard tool to help you with that.
-
WebGPU hits 40% availability 2 weeks after Chrome releases support
As someone else pointed out, you're overestimating Chrome/ium's market share.
Regardless, after the web.dev/baseline announcement, I looked at Browslerlist and one of our site's analytics and it is shocking how many people are not using the last two versions of evergreen browsers. There is a long tail of browser versions in those stats.
https://browsersl.ist
-
Baseline: a unified view of stable web features
The way folks handle this in production is with browserslist, which lets you query on different things you want to support: https://github.com/browserslist/browserslist. This in turn tells other parts of your tooling what language features to transpile for production.
I imagine tools could be built on top of that which do what you’re asking too
What are some alternatives?
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
autoprefixer - Parse CSS and add vendor prefixes to rules by Can I Use
rollup-plugin-ts - A TypeScript Rollup plugin that bundles declarations, respects Browserslists, and enables seamless integration with transpilers such as babel and swc
caniuse - Raw browser/feature support data from caniuse.com
fusionjs - Modern framework for fast, powerful React apps
rollup-plugin-terser - Rollup plugin to minify generated bundle