ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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.
How Rollup decides which modules to drop, why package.json sideEffects is a trust boundary, and the checks that catch a wrong declaration before users do.
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.
Rollup's tree-shaking only removes dead code when packages correctly declare sideEffects in package.json. Learn how to configure it, verify the pruning, and avoid common pitfalls that leave unused functions in your production bundle.
Lodash / Lodash‑ES Integration In a monorepo or multi‑project setup, developers often import from both lodash (CommonJS) and lodash-es (ESM). The goal is to maintain a repeatable build that is both size‑efficient and type‑safe across webpack, Rollup, and other bundlers. Goal: Repeatable Development Environment We need a strategy that guarantees deterministic
Rollup builds a static module graph from ES module import and export declarations and uses that graph for tree-shaking and code splitting. The goal is to clarify the documented decision rules for which exports are considered unused and removed, and which modules are emitted into separate chunks for lazy loading. Constraints include purely static analysis wit
Diagnosing duplicate root-provided service instances A service decorated with providedIn: 'root' should resolve to a single instance within the root EnvironmentInjector tree. In a standalone Angular 17+ application using loadComponent() for lazy routes, the same service class appears in multiple lazy chunks after production build, causing separate constructo
rollup
javascript
chartjs
corejs
lodash
angular