Cut build output: remove unused code and split bundles
A build artefact heavier than it needs to be, reduced with size measured either side.
The ticket
Reduce build output size through pruning, tree-shaking, and splitting.
Acceptance criteria
- Size is measured before and after
- Removed code is confirmed unused
- Behaviour is unchanged, proven by the suite
- The largest remaining contributors are listed for follow-up
What lands as proof
Size measurements either side plus a green suite, so the reduction is not paid for in behaviour.
Why teams defer it
- Size grows gradually and nobody owns the total.
- Tree-shaking fails silently on side-effectful modules, so the savings are smaller than the tooling promises.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: reduce build output size through pruning, tree-shaking, and splitting. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means size measured before and after in the pull request, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.