본문으로 바로 가기
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

앱에 내장된 스냅샷을 표시하고 있습니다(콘텐츠 소스가 설정되지 않았습니다). 소스에는 더 새로운 콘텐츠가 있을 수 있습니다.