Comparison
Bundle analysisvsModule graph
Bundle analysis
you generated the treemap and found one dependency taking up a third of the bundle.
Visualising what each module contributes to the output, usually as a treemap of the module graph. It is the only reliable way to answer 'why is this bundle 900 kilobytes', because the answer is nearly always one or two things and nearly never what you guessed. Read the compressed sizes rather than the raw ones, since those are what the user actually downloads.
Full entry →Module graph
you imported one helper and the build pulled in a date library you have never used directly.
The directed graph of every module reachable from the entry points, which is the exact set the bundler must account for. Bundle size is a property of this graph rather than of your own code, so one transitive import can dominate the output. Reading it is the first step of every size investigation, which is what a bundle analyser is for.
Full entry →