Choosing core-js polyfills: full bundle or targeted imports
Decide between full core-js, modular feature imports, and Babel usage-based polyfills based on bundle size and target browsers.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide between full core-js, modular feature imports, and Babel usage-based polyfills based on bundle size and target browsers.
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.
Add runtime polyfills for finished ECMAScript features with core-js v3 stable while keeping syntax transforms separate.
Add Array.prototype.flatMap support to legacy browsers with core-js. Follow this guide to install, import, and verify the polyfill while keeping bundle size and performance in check.
Configure Babel 7 to down‑compile syntax only for browsers that need it and inject core‑js 3 polyfills only where used, with steps to verify and recover from common misconfigurations.
Learn how to configure browserslist and import only the core-js polyfills your target browsers actually need, reducing bundle size without sacrificing compatibility.
Stop bloating your JS bundles with unnecessary polyfills. Learn how to use Babel's useBuiltIns: 'usage' to inject only the code your target browsers actually need.
Learn how to set up Babel preset-env with useBuiltIns: usage to transpile ES2015+ code while injecting only the polyfills actually needed for your target browsers.
Learn how to add a reliable Promise.allSettled polyfill using core-js, see a concrete example, and understand the trade-offs before adding it to your bundle.