Stop Shipping the Whole core-js Library: Use Modular Polyfill Imports
Stop shipping every core-js polyfill. Import only the ECMAScript features your app uses and verify the savings in your production bundle.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop shipping every core-js polyfill. Import only the ECMAScript features your app uses and verify the savings in your production bundle.
Learn how Angular standalone components eliminate NgModule boilerplate, simplify bootstrapping, and improve tree‑shaking, with a concrete example and common pitfalls to avoid.
Stop shipping all of core-js/stable. Choose the right CoreJS entry point, wire up Babel's useBuiltIns: 'usage', and verify the bundle actually shrank.
Global polyfills bloat bundles and mutate prototypes. Learn how core-js/pure with Babel's usage mode injects only the polyfills your code actually needs, with config, example, and pitfalls.
Your bundle ships 70 KB of Lodash but you use five functions. Diagnose which import pattern is defeating tree-shaking, fix it, and verify with the bundle analyzer.
Learn how to shrink ClojureScript output by turning on advanced compilation and letting the compiler infer externs, with a step‑by‑step Reagent example and verification tips.
Learn how React Server Components let you render UI on the server, stream HTML, and cut client‑side JavaScript without rewriting your app.
Learn how to shrink your ClojureScript bundle with Shadow CLJS’s :advanced compiler mode. A step‑by‑step guide covers config, externs, pitfalls, and verification to keep your production build fast and reliable.
Babel duplicates helper functions in every file by default. @babel/plugin-transform-runtime moves those helpers to shared imports from @babel/runtime, reducing bundle size and making polyfills explicit.