Imported one lodash function but got the entire library in my bundle. Making tree shaking actually work requires understanding ES modules.
Optimizing by gut feeling made my app slower. Learn to use Performance profiler to find real bottlenecks and fix what matters.
Text to Binary (HTTP/2), TCP to UDP (HTTP/3). From single-file queueing to parallel processing. Google's QUIC protocol story.
From HTML parsing to DOM, CSSOM, Render Tree, Layout, Paint, and Composite. Mastering the Critical Rendering Path (CRP), Preload Scanner, Reflow vs Repaint, and requestAnimationFrame.
Obsessively wrapping everything in `useMemo`? It might be hurting your performance. Learn the hidden costs of memoization and when to actually use it.
Now I can summarize.
For tree shaking to work:
import/export, not CommonJSimport { fn } > import libmodule field)sideEffects: falseexports fieldTree shaking isn't magic. Write code that build tools can statically analyze, and they'll automatically drop dead code. To properly shake a tree, you need to plant it in a way that allows shaking. That was the key insight.