skip to content

Tree-Shaking

0 questions

Dead-code elimination that works because ESM imports are statically known: what makes a module side-effect-free, what the sideEffects package flag promises, and how Rollup, webpack and esbuild decide an export is unused. Asked because bundle size is a real budget, and 'why is this whole library in my bundle' usually traces to a side effect or a CommonJS dependency.

questions

no questions here yet

this part of the tree is still being written

>
0 questions in this topic or below it