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.
Este recurso está disponível apenas em inglês.
Prompts são textos que você copia para o seu próprio assistente. O KitLocal não os executa.
Preencha as variáveis
O que você digita fica neste navegador. Não é adicionado à URL, salvo nem enviado a lugar nenhum.
Pré-visualização
Ainda falta: 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}}
```
Finalidade
Catch server/client boundary mistakes in Next.js App Router code before they become runtime errors or bundle bloat.
Quando usar
- You added or moved a component and are unsure where "use client" belongs.
- A page hydrates oddly or the client bundle grew.
O que preparar
- The component (and its direct imports if short), plus the Next.js version.
Saída esperada
A numbered list (items 1-6) with verdict, evidence and a minimal diff where needed.
Sobre este catálogo
Instantâneo incluído · publicado 15 de nov. de 2026, 06:05 · Revisão do catálogo 5bc079fe355af2214bc0
Mostrando o instantâneo incluído no aplicativo (nenhuma fonte de conteúdo está configurada). Pode haver conteúdo mais recente na fonte.