跳至主要內容
kitlocal.dev

Review a Next.js component for server/client boundaries

Checks an App Router component for misplaced "use client", leaked server-only code, hydration risks and avoidable client bundle weight.

此資源僅提供英文版本。

提示詞是你複製到自己助理中的文字。KitLocal 不會執行它們。

填寫變數

你輸入的內容只保留在此瀏覽器中,不會加入 URL、儲存或傳送到任何地方。

預覽

仍需填寫:Component code

Review this Next.js (version 16, App Router) component.
Cache Components enabled: no

Check and report, with line references:
1. Is "use client" necessary, and is it as low in the tree as possible?
2. Does any client code import server-only modules, secrets, or Node built-ins?
3. Can browser-only values (window, localStorage, Date.now, Math.random) cause a hydration mismatch?
4. Are props crossing the server → client boundary serializable?
5. Are there heavy dependencies that could be loaded lazily?
6. Are params / searchParams / cookies / headers handled with the async APIs for this version?
Answer "no issue" explicitly for items that are fine. Do not rewrite the file unless asked;
propose minimal diffs.

```tsx
{{component}}
```

用途

Catch server/client boundary mistakes in Next.js App Router code before they become runtime errors or bundle bloat.

適用時機

  • You added or moved a component and are unsure where "use client" belongs.
  • A page hydrates oddly or the client bundle grew.

需要準備的內容

  • The component (and its direct imports if short), plus the Next.js version.

預期輸出

A numbered list (items 1-6) with verdict, evidence and a minimal diff where needed.

關於此目錄

內建快照 · 發布於 2026年11月15日 清晨6:05 · 目錄修訂版 5bc079fe355af2214bc0

正在顯示應用程式內建的快照(尚未設定內容來源)。來源處可能已有更新的內容。