Avoid server/client boundary leaks in Next.js

#Metadata

Rule ID

ts.next.no-server-client-boundary-leaks

Severity

high

Confidence

0.8

Languages

javascript, typescript

Presets

strict

Stability

experimental

Applies to

file

Tags

correctness, next, react, rules-catalog

#Why it matters

Browser globals and client-only hooks break server rendering boundaries and make component intent unclear.

#Remediation

Add `'use client'` or move the code into a client component or hook.

#Repository path

The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.next.no-server-client-boundary-leaks.rule.yaml.