ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Babel’s useBuiltIns option in @babel/preset‑env lets you auto‑inject polyfills only for the features you actually use. This reduces bundle size, speeds up load times, and keeps your codebase lean. Learn how to configure it, see a concrete example, and understand the trade‑offs.
Learn how to turn on Rollup’s built‑in tree‑shaking, verify that unused exports are removed, and recover if needed code is dropped.
Learn how to use Rollup’s output.plugins hook to generate deterministic, readable filenames for code‑split chunks while avoiding collisions and preserving cache‑busting benefits.
Rollup's tree shaking uses ES Module static structure to drop unused exports. Learn how the treeshake config tunes aggressiveness, why sideEffects flags matter, and how to verify the output in CI.
A systematic diagnostic sequence for Rollup's three most common failures: unresolved modules, missing exports, and unexpected bundle bloat — with fixes tied to each finding.
Chart.js 4 removes auto-registration. Import only the controllers, scales, elements, and plugins you need, register them explicitly, and let your bundler tree-shake the rest. A minimal line chart with decimation drops to ~20 kB gzipped.
A decision guide to Rollup code splitting: when to use entry-point chunks, a manualChunks function, or preserveModules, with working configs and validation steps.
Learn how Rollup’s tree‑shaking can trim unused code from your library, the pitfalls to avoid, and a step‑by‑step example that shows real bundle size gains.
Learn how to use Core‑JS 3.x to polyfill only the features you need. This guide shows the difference between <code>pure</code> and <code>stable</code> imports, walks through a Promise polyfill example, and explains how to keep your bundle lean.
javascript
rollup
chartjs
corejs