Autoprefixer + Browserslist: Smarter Vendor Prefixing for CSS
How to configure Autoprefixer with Browserslist so CSS supports target browsers without unnecessary prefix bloat.
Loading…
ReadMeFeed / Community knowledge
#browserslist
Real questions. Useful conversations. Find the people who know your stack.
postcssFine‑grained polyfills with @babel/preset-env and useBuiltIns: usage
Learn how Babel’s preset-env can inject only the polyfills you actually need, based on your browserslist targets, and see the trade‑offs of the usage mode.
Ship fewer core-js polyfills by matching imports to your browser targets
Stop shipping every core-js polyfill to every browser. Use core-js-compat with browserslist to import only the ECMAScript polyfills your supported targets actually need.
corejsDiagnosing Babel preset-env Target Mismatches That Ship Modern Syntax to Old Browsers
Builds pass and dev works, but production users see immediate SyntaxError for optional chaining or class fields. Learn to diagnose browserslist and preset-env target mismatches.
javascriptDiagnosing Missing Vendor Prefixes in PostCSS Autoprefixer Builds
A step‑by‑step diagnostic guide for figuring out why PostCSS Autoprefixer is not adding vendor prefixes and how to fix it.
Diagnosing Babel preset-env Misconfiguration That Breaks Legacy Browser Builds
A step-by-step diagnostic guide for identifying why @babel/preset-env fails to transform syntax or inject polyfills for older browsers, including ordered checks and targeted fixes.
Babel preset-env targets: stop transpiling what browsers already run
A tight target query is what keeps @babel/preset-env from rewriting syntax your users already run. Diff two target sets, keep ES modules for the bundler, and verify the result.
Selective core-js Polyfills with browserslist: A Practical Engineering Guide
Learn how to configure browserslist and import only the core-js polyfills your target browsers actually need, reducing bundle size without sacrificing compatibility.
Adding Minimal core-js Stable Polyfills Without Shipping Unstable Proposals
Import core-js's stable entry point once at application startup, let browserslist drive the included features, and avoid unstable proposal polyfills that change behavior between releases.