ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context A Chart.js v3 configuration that renders correctly when loaded via a full UMD bundle in development can fail after a production build with tree-shaking enabled. The ES module entry point does not automatically export or register controllers, elements, scales, or plugins; each must be explicitly imported and registered with Chart.register() . Bundlers
Goal Minimize the amount of data transferred for a single page that receives a small number of visits per month. Constraints & Uncertainty Rollup removes unused ES module exports by default, but the extent of size reduction depends on side‑effect annotations and the presence of dynamic imports. Manual chunks can split the bundle into route‑specific piece
Interoperability gap Rollup's treeshake.moduleSideEffects defaults to 'no-external' , treating external dependencies as side-effect-free unless a package declares sideEffects: false or an array in its package.json . Local development servers (Vite, webpack dev middleware) frequently disable aggressive tree-shaking to preserve HMR, which masks side-effect bug
Goal is to configure a Rollup library build that maximizes downstream tree-shaking while keeping the declared public API intact. Static tree-shaking relies on ES module syntax and accurate sideEffects metadata, and code splitting is driven by dynamic import() with manualChunks shaping. Output format choice between es and cjs changes interop helpers and expor
This build configures Rollup to tree-shake an ES-module bundle for a low-traffic site. The goal is to confirm that unused exports are removed based on side-effect analysis, and to understand whether retained code is expected behavior or a configuration gap. Rollup documentation indicates tree-shaking depends on accurate side-effect detection for imported fil
CSS imports missing in webpack 5 production builds Goal: Determine how webpack 5 should interpret a missing sideEffects field in package.json when deciding whether to preserve CSS imports during production‑mode tree shaking. In development mode, webpack does not apply sideEffects‑based tree shaking, so CSS imports remain in the bundle regardless of the field
Runtime Style Injection Overhead Ant Design v5 transitioned from Less to a CSS-in-JS architecture via @ant-design/cssinjs . While this enables dynamic theming through Design Tokens, it introduces a runtime style injection layer that increases the baseline JavaScript bundle size compared to the static CSS approach used in v4. Tree-Shaking and Import Patterns
rollup
webpack
antdesign
chartjs
vite