What 'No JS' Really Means: The Nuance
You'll learn: Why "Server Components ship no JavaScript" is technically true but doesn't mean React itself disappears from the client.
The Marketing vs Reality
When you hear "Server Components send zero JavaScript," that's accurate—but it requires precision. Server Components themselves contribute no code to your client bundle. However, your application still needs the React runtime to handle Client Components, interactivity, and state management.
Think of it like a car factory: Server Components are parts manufactured at the factory (server) and shipped fully assembled. Client Components are parts that need assembly instructions (JavaScript) included in the box. The customer (browser) still needs tools (React runtime) to assemble Client Components, but Server Components arrive ready-to-use with no assembly required.
What Actually Ships
- Server Components: Pure rendered output in the RSC wire format. No component code, no logic, no event handlers.
- Client Components: Full component code plus the React runtime to execute them.
- React Runtime: Always present if you have any Client Components or interactivity.
A page with 100% Server Components still includes React's runtime for hydration coordination and potential future updates. The win is that those 100 components don't add their own code—just React's core.
The Real Savings
If your Server Component imports a 200KB library to render a chart, that 200KB never reaches the browser. Replace ten Client Components with Server Components? You eliminate their individual code, but React itself remains.
Key Takeaway: "No JS" means no component-specific code from Server Components, not literally zero JavaScript on the page—React's runtime still powers your Client Components and orchestrates updates.