burokku
browserslist
| burokku | browserslist | |
|---|---|---|
| 1 | 55 | |
| 6 | 12,741 | |
| - | 0.7% | |
| 7.9 | 7.8 | |
| 13 days ago | 2 months ago | |
| JavaScript | JavaScript | |
| - | 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.
burokku
-
When Vite ignores your Browserslist configuration
The steps described here can also be vizualized in a commit of mine.
browserslist
- 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
- Browserslist
-
Configure Stimulus with esbuild and Babel — Rails & Javascript
# .browserslist.rc # Babel Preset configuration # -------------------------- # Defines web-browser compatibility parameters for Babel to transpile your JS code. # This configuration is used by babel.config.js. # More information in here. # https://github.com/browserslist/browserslist # Support browsers with a market share higher than 5% >10%
What are some alternatives?
browserslist-to-esbuild - Get esbuild-compatible targets from a browserlist config or project
autoprefixer - Parse CSS and add vendor prefixes to rules by Can I Use
esbuild - An extremely fast bundler for the web
parcel - The zero configuration build tool for the web. 📦🚀
esbuild-plugin-browserslist - Configure esbuild targets based on a browserslist query
caniuse - Raw browser/feature support data from caniuse.com
vite - Next generation frontend tooling. It's fast!
rollup-plugin-postcss - Seamless integration between Rollup and PostCSS.
EmulatorJS - The official home of the EmulatorJS project
ECMAScript 6 compatibility table - ECMAScript compatibility tables
rollup-plugin-terser - Rollup plugin to minify generated bundle
react-typescript-webpack-starter - A starter project for using React, TypeScript, SCSS using Webpack 5.