Comparison
Bundle analysisvsBundle budget
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 →Bundle budget
the build fails when the main chunk goes over the number the team agreed on.
An enforced limit on the size of the shipped assets, checked in CI so growth has to be argued for rather than accumulating. It works because bundle size never regresses in one large jump; it regresses by ten kilobytes at a time until someone measures. A budget without a failing build is a wish, and one set above the current size does nothing at all.
Full entry →