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.
Questa risorsa è disponibile solo in inglese.
I prompt sono testo che copi nel tuo assistente. KitLocal non li esegue.
Compila le variabili
Quello che scrivi resta in questo browser. Non viene aggiunto all’URL, salvato né inviato da nessuna parte.
Anteprima
Ancora necessario: 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}}
```
Scopo
Catch server/client boundary mistakes in Next.js App Router code before they become runtime errors or bundle bloat.
Quando usarlo
- You added or moved a component and are unsure where "use client" belongs.
- A page hydrates oddly or the client bundle grew.
Cosa preparare
- The component (and its direct imports if short), plus the Next.js version.
Output atteso
A numbered list (items 1-6) with verdict, evidence and a minimal diff where needed.
Informazioni su questo catalogo
Istantanea inclusa · pubblicato 15 nov 2026, 06:05 · Revisione del catalogo 5bc079fe355af2214bc0
Viene mostrata l’istantanea inclusa nell’app (nessuna fonte di contenuti configurata). Alla fonte potrebbero esserci contenuti più recenti.