0Pricing
Next.js 15 Fullstack (App Router + Server Actions) · 课时

服务器组件与客户端组件的组合模式

学习如何正确组合服务器组件和客户端组件,将服务器组件作为子组件传入,避免客户端构建包过度膨胀。

服务器组件与客户端组件的组合模式 是 CoddyKit 上的免费 Next.js 15 Fullstack (App Router + Server Actions) 课时。 这是第 4 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Next.js 15 Fullstack (App Router + Server Actions) 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

The Composition Challenge

You often need interactivity (Client) wrapping data-heavy UI (Server). The trick is composing them so Server Components are not pulled into the client bundle.

The One-Way Rule

A Client Component cannot import a Server Component, because importing would force it to run on the client. But it can render one passed as children.

Passing as Children

Render a Server Component inside a Client Component by passing it through props from a parent Server Component.

export default function Page() {
  return (<ClientShell><ServerContent /></ClientShell>);
}

The Client Shell

The Client Component receives the already-rendered Server output as children and never needs to know how it was built.

"use client";
export default function ClientShell({ children }) {
  const [open, setOpen] = useState(false);
  return (<div>{children}<button onClick={() => setOpen(!open)}>Toggle</button></div>);
}

Why This Works

The Server Component renders on the server; only its output (serialized RSC payload) reaches the client. The Client Component just slots it in — no server code shipped.

Props Must Be Serializable

Props passed from Server to Client Components must be serializable. You cannot pass functions, class instances, or Dates without care — but you can pass plain data and JSX children.

Moving Client Boundaries Down

Keep "use client" as deep in the tree as possible. A small leaf Client Component keeps most of the tree server-rendered and the bundle small.

Context Providers

Client context providers wrap Server children fine: define the provider as a Client Component and pass server-rendered children through it.

"use client";
export function ThemeProvider({ children }) {
  return <Ctx.Provider value={theme}>{children}</Ctx.Provider>;
}

Avoiding Accidental Client Code

Importing a library that uses browser APIs into a Server Component breaks it. Isolate such code behind a Client Component boundary.

Interleaving Example

You can deeply interleave: Server layout, Client sidebar toggler, Server content, Client like-button — each boundary minimal and intentional.

Mental Model

Think of Client Components as holes in a server-rendered tree. Data flows down as props/children; interactivity lives only where needed.

Quick Check

How do you render a Server Component inside a Client Component?

Recap

You learned the key composition pattern: Client Components cannot import Server Components but can render them as children. Keep client boundaries small and deep, pass serializable props, and treat Client Components as interactive holes in a server-rendered tree.

常见问题解答

「服务器组件与客户端组件的组合模式」课时是免费的吗?

是的 — 「服务器组件与客户端组件的组合模式」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Next.js 15 Fullstack (App Router + Server Actions) 课程的其余内容,请升级到 CoddyKit PRO。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。

「服务器组件与客户端组件的组合模式」这节课中我会学到什么?

学习如何正确组合服务器组件和客户端组件,将服务器组件作为子组件传入,避免客户端构建包过度膨胀。 你通过在浏览器中直接运行的动手代码来练习 Next.js 15 Fullstack (App Router + Server Actions),全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Next.js 15 Fullstack (App Router + Server Actions) 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Next.js 15 Fullstack (App Router + Server Actions) 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 4 节课,共 4 节。

「服务器组件与客户端组件的组合模式」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Next.js 15 Fullstack (App Router + Server Actions) 课中编写并运行代码吗?

能。每节 Next.js 15 Fullstack (App Router + Server Actions) 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 理解 RSC 与 RCC
  2. 在 RSC 中获取数据
  3. 使用 RCC 实现交互
  4. 服务器组件与客户端组件的组合模式
← 返回 Next.js 15 Fullstack (App Router + Server Actions)