The Symbol.for('react.element') Exception
What you'll learn: Why JSX elements (React elements) are the special exception that can cross the server-client boundary as props.
The Serialization Exception
You've learned that functions can't be serialized and passed from server components to client components. But there's one crucial exception: JSX elements themselves.
When you write <ServerComponent />, React creates an object with a special symbol: Symbol.for('react.element'). This marks it as a React element. Even though this object looks like it contains functions (component definitions), React treats it differently during serialization.
Why This Works
Think of JSX as a "render instruction" rather than raw data. When you pass <ServerComponent /> as a prop to a client component, you're not passing the component function—you're passing the already-rendered output from the server.
// Server Component
async function ServerData() {
const data = await db.query();
return <div>{data}</div>;
}
// Client Component
'use client';
function Wrapper({ children }) {
return <div className="wrapper">{children}</div>;
}
// This works!
<Wrapper>
<ServerData />
</Wrapper>
The <ServerData /> element gets rendered on the server, and its output crosses the boundary—not the function itself.
The Practical Impact
This exception is what makes the composition pattern work. You can nest server components inside client components by passing them as children or any other prop. The client component doesn't execute the server component; it just positions the pre-rendered result.
Key Takeaway: React elements (JSX) are serializable because they represent already-rendered output, not executable functions—this is the exception that enables server-client composition.