Learning on Web Dev Open is free for all.

Framework Internals > The App Router, and where the seams areAudit your own boundaries
Phase 04The App Router, and where the seams are231 of 434

Audit your own boundaries

Measure what you actually shipped to the browser, then cut it by a third without removing a feature.

Solo project90 minAI pair

Done when

  • A before-and-after measurement of client JavaScript per route
  • At least a third less shipped JavaScript on your heaviest route
  • Every remaining client component has a one-line justification
  • All existing behaviour still works, demonstrated by a test or a recorded walkthrough

Nobody marks this for you. It goes into your phase checkpoint, where a person does.

You should now be able to

  • Attribute every kilobyte of your client bundle to a decision
  • Reduce shipped JavaScript measurably and prove nothing broke
Ask the community

Loading…

← PreviousBuild the thing, properlyThe App Router, and where the seams areNext →Explain one internal, from the sourceThe App Router, and where the seams are