Ir al contenido principal
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.

Este recurso solo está disponible en inglés.

Los prompts son texto que copias en tu propio asistente. KitLocal no los ejecuta.

Rellena las variables

Lo que escribes se queda en este navegador. No se añade a la URL, ni se guarda, ni se envía a ningún sitio.

Vista previa

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}}
```

Propósito

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

Cuándo usarlo

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

Qué preparar

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

Salida esperada

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

Acerca de este catálogo

Instantánea incluida · publicado 15 nov 2026, 6:05 · Revisión del catálogo 5bc079fe355af2214bc0

Mostrando la instantánea incluida en la aplicación (no hay ninguna fuente de contenido configurada). Puede haber contenido más reciente en la fuente.