ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Hardcoded Babel targets either bloat your bundle or break old browsers. Here's how browserslist-driven preset-env config, core-js injection, and the debug flag turn transpilation into an auditable decision.
Configure @babel/preset-env with useBuiltIns: 'usage' and core-js 3 so Babel injects only the polyfills your browserslist targets need — plus how to verify and roll back.
Adopt CSS nesting and other future features without breaking old browsers by transforming them with PostCSS and postcss‑preset‑env. Learn the pipeline, see a concrete example, and weigh the trade‑offs before adding the build step.
If your Babel bundle still contains arrow functions even though you target modern browsers, this guide walks you through diagnosing the mismatch, checking config files, and applying the right fixes to get pure ES5 output.
Learn how PostCSS Preset Env lets you write nesting, custom media, and logical properties today while automatically generating fallbacks for the browsers you support.
Learn how to install and configure PostCSS Preset‑Env to automatically polyfill modern CSS based on a browserslist query, with a worked example and common pitfalls.
A decision guide for core-js 3.x polyfills under browserslist: compare global stable, selective ES imports, core-js-pure and bundler automation, with trade-offs and a concrete per-feature import pattern.
Vite + @vitejs/plugin‑legacy: Target Decision for Zero‑Downtime Migration Migrating a lightweight application to Vite while preserving uninterrupted service requires careful handling of the legacy bundle. The @vitejs/plugin‑legacy module produces a separate ES5‑compatible script that is loaded via a <script nomodule> tag, allowing modern browsers to co
corejs
postcss
vite