Tree-Shaking Dependency Graph Pruner

Entry Point

Tree-shaking (DFS prune)

Minify kept code (−38%)

New dependency edges to add 1

Bundle Size

Kept 0 KBPruned 0 KB

Modules reachable

0 / 0

Final bundle

0 KB

Raw source size

0 KB

Size reduction

How it works

Every JS/RN/Flutter module is a node; an import is a directed edge. Tree-shaking is graph reachability: a bundler runs depth-first search from the entry point and keeps only modules actually reachable, discarding everything else as dead code.

reachable = DFS(entry)
kept_size   = Σ size(m) for m in reachable
pruned_size = Σ size(m) for m in (all - reachable)
if minify:  kept_size *= (1 - 0.38)   // R8/ProGuard-style shrink
reduction%  = 1 - final_bundle / raw_source_size

Entry point — pick which screen/feature boots the DFS; a different entry reaches a different subgraph, so the same codebase ships a different bundle per split.
Tree-shaking toggle — off ships every module regardless of reachability, exactly like a bundler with dead-code elimination disabled.
Minify toggle — an extra flat 38% cut on the kept modules only, modelling ProGuard/R8 or Terser minification on top of pruning.
Add random dependency — wires a new import edge into the graph (simulating adding an npm/pod package); if it hangs off an already-unreachable node it costs nothing until something reachable imports it.

Real-world relevance: this is exactly what Metro (React Native), Webpack/Rollup and Android's R8 do to produce the shipped mobile app bundle — unreachable modules never leave the build server.

Entry point Reachable (kept) Unreachable (pruned)

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.