The anatomy of crossing the network boundary
A web app is one program that runs across two computers — a server and a client — separated by a network boundary. Bundling decides where code runs, when it runs, and what actually crosses: real data, rendered output, or only a reference. Click any block in the diagram, any concept card, or any highlighted term to open it up.
One program, two computers
A web app is one program split across a server chip and a client chip, joined by a single network wire. The build compiles once and splits the graph at the 'use client' frontier; then one request traces the whole lifecycle — render down the server, cross the wire, paint and hydrate the client, and loop back on a Server Action. Trace weight shows what crosses: nothing from the server but data, the payload across, the heaviest JavaScript at hydration.
signal = one request · trace weight = what crosses · hairline on the server, heaviest at hydration · the loop closes on the round-trip
Eleven concepts, head to toe
Each card opens a full detail panel — verbatim explanation, code, and an interactive trace you can scrub. Same panels open from the diagram above.
Glossary
Every highlighted term across the page resolves here. Click one to pin its definition; many definitions link onward to others.