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日 06:05 · 目录修订版 5bc079fe355af2214bc0
正在显示应用内置的快照(未配置内容来源)。来源处可能已有更新的内容。