Next.js — Pages Router
Two pieces from @devtools/next: withNekutaSSR() wraps getServerSideProps, and NekutaAppProvider wraps your _app.tsx.
Next.js — App Router
There's no persistent "app instance" in the App Router the way Pages Router has _app.tsx — Server Components render per-request, and state has to cross an explicit Server → Client boundary. Two pieces from @devtools/next handle this: getServerNekuta() (a Server Component helper) and `` (the Client Component boundary).
Hydration & skipHydrate
Both Next.js adapters rely on the same three functions from nekuta (not @devtools/next — this logic is router-agnostic, the adapters only handle transporting the result):