Next.js App Router Prefetch and Hydration Keep server rendering while gaining a live client cache
Phase 22 - TanStack Query Volume 06 - Professional Frontend
Preserve Server Components with hydration A common migration mistake is adding useQuery directly to a page and converting the entire route to a Client Component. Next.js App Router and TanStack Query can work together: the Server Component can prefetch, dehydrate the cache, and a smaller Client Component can subscribe to the same query.
request-scoped QueryClient
prefetchQuery(taskListOptions)
dehydrate(queryClient)
// app/(app)/tasks/page.tsx - Server Component
import { dehydrate, HydrationBoundary } from "@tanstack/react-query";
import { getQueryClient } from "@/lib/query/get-query-client";export default async function TasksPage({ searchParams }: PageProps) {
const query = normalizeTaskSearchParams(await searchParams);
const queryClient = getQueryClient();await queryClient.prefetchQuery(taskListOptions(query));return (
<HydrationBoundary state={dehydrate(queryClient)}>
<TasksScreen query={query} />
</HydrationBoundary>
);
}The server-side query function must be able to forward the current Supabase access token to NestJS. The browser query function can acquire the browser session token. Keep these transport details behind environment-appropriate API client helpers rather than making every component understand cookies and bearer headers.
Set a non-zero staleTime for hydrated data Without a freshness window, the client can immediately consider the hydrated result stale and refetch as soon as it mounts. The official App Router guidance recommends a staleTime above zero for this pattern.
Avoid rendering the same mutable query data independently in a Server Component and a Client Component if the client can later refetch it. The two surfaces can drift. Prefer the Server Component as a preloader and the Client Component as the owner of data that will revalidate in the browser.
Do not prefetch everything Server prefetch is most valuable for above-the-fold data that materially improves the first render. Low-priority panels can remain ordinary client queries. Prefetching every possible query increases server work and hydration payload without necessarily improving the experience.
Next.js is useful only when you can explain what runs on the server, what crosses into the browser, and which route owns a user-visible state.
Restate the goal of “Next.js App Router Prefetch and Hydration” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: route → Server Component → client boundary → request/data source → rendered UI. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: TaskFlow query/mutation layer with stable keys, list/detail caching, invalidation, filters, and debugging via devtools/logs.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
// app/tasks/page.tsx
import { TaskList } from "./task-list";
export default async function TasksPage() {
const tasks = await loadTasks();
return <TaskList initialTasks={tasks} />;
}Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Locate the first browser-only API or stateful hook and move the client boundary to the smallest component that needs it.
Verify route params, fetch location, cache behavior, and the exact server response before changing JSX.
Without copying the final source, create a second small scenario that applies “Next.js App Router Prefetch and Hydration” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Move task-list fetching into query options and observe loading/error/success/cache states.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Random query-key arrays scattered through components
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.