React Router 7 Typegen Route Hydration and Single-Fetch Streaming Boundaries

--- description: React Router 7 Typegen Route Hydration and Single-Fetch Streaming Boundaries - Enforces strict typegen module contracts, turbo-stream single-fetch data boundaries, and safe clientLoader hydration patterns in React Router 7 framework mode. Prevents hydration mismatches, double data fetching during hydration, and deprecated v2 defer/json abstractions. globs: app/**/+types/**/*.{ts,tsx}, app/routes/**/*.{ts,tsx}, app/root.tsx alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/rr7-hydration-single-fetch-streaming-guardrail" --- # React Router 7 Typegen Route Hydration and Single-Fetch Streaming Boundaries > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Using deprecated json()/defer() helpers and uncoordinated clientLoaders causing hydration waterfall flashes ## System Constraints You are a Principal Engineer enforcing React Router 7 Framework Mode Hydration invariants. Mandate typegen route modules (+types), native single-fetch serialization (no legacy json()/defer()), precise clientLoader hydration flags, and strict Suspense/Await boundaries for deferred stream promises. ## Strict Guidelines - Engineers MUST ALWAYS import route types directly from the collocated typegen artifacts (e.g., `./+types/[route-file]`) for Route.LoaderArgs, Route.ComponentProps, and Route.ActionArgs. - Engineers MUST NOT use deprecated Remix v2 data utilities such as `json()` or `defer()`; React Router 7 Single Fetch natively serializes raw plain objects, Dates, Maps, Sets, and unresolved Promises via turbo-stream. - Engineers MUST explicitly set `clientLoader.hydrate = true` only when the client loader is intentionally designated to run on initial document load, and MUST handle `serverLoader` cache hand-offs without creating client-side network waterfalls. - Components consuming un-awaited loader promises MUST wrap consumption within `<React.Suspense>` and `<Await resolve={...}>` to prevent blocking the initial HTML stream. - Loaders MUST NOT serialize supported rich types (Date, BigInt, Map, Set, Error) into strings or JSON mocks manually, as turbo-stream preserves exact JS prototype fidelity across the wire. ## Bad vs Good Implementations ### React Router 7 Route Data Loading and Streaming Hydration Contract #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Uses legacy Remix v2 defer()/json() methods incompatible with RR7 Single Fetch, manually stringifies dates/JSON objects, omits typegen Route contracts, and fails to configure clientLoader.hydrate, leading to hydration thrashing. ```typescript import { defer, json } from '@remix-run/node'; // DEPRECATED in RR7 Framework Mode import { useLoaderData } from '@remix-run/react'; export async function loader({ params }: any) { const critical = await fetchCriticalData(params.id); const slowPromise = fetchSlowMetrics(params.id); // ANTI-PATTERN: Using legacy defer() and manual JSON serialization return defer({ critical: JSON.stringify(critical), metrics: slowPromise, renderedAt: new Date().toISOString() }); } // ANTI-PATTERN: Missing hydrate flag causes clientLoader to re-fetch on every hydration export async function clientLoader({ serverLoader }: any) { return serverLoader(); } export default function RouteComponent() { const data = useLoaderData() as any; // ANTI-PATTERN: Untyped data without typegen return <div>{data.critical}</div>; } ``` #### Production Standard (Correct) > **Standard**: Adheres to RR7 framework invariants: imports Route types from collocated typegen (+types/dashboard), utilizes naked object returns for Single Fetch streaming, preserves native Date instances, explicitly defines `clientLoader.hydrate = true`, and wraps streamed promises in Suspense/Await boundaries. ```typescript import { Suspense } from 'react'; import { Await } from 'react-router'; import type { Route } from './+types/dashboard'; export async function loader({ params }: Route.LoaderArgs) { const critical = await fetchCriticalData(params.id); const slowMetricsPromise = fetchSlowMetrics(params.id); // RR7 Single Fetch natively returns raw objects and streams un-awaited promises return { critical, slowMetrics: slowMetricsPromise, renderedAt: new Date() // Turbo-stream preserves Date prototypes natively }; } // Explicitly opt-in to running clientLoader on document hydration only when necessary export async function clientLoader({ serverLoader }: Route.ClientLoaderArgs) { return await serverLoader(); } clientLoader.hydrate = true as const; export default function DashboardRoute({ loaderData }: Route.ComponentProps) { return ( <main> <h1>Critical Data: {loaderData.critical.title}</h1> <p>Rendered: {loaderData.renderedAt.toLocaleTimeString()}</p> <Suspense fallback={<div>Loading deferred metrics...</div>}> <Await resolve={loaderData.slowMetrics}> {(metrics) => <div>Metrics Score: {metrics.score}</div>} </Await> </Suspense> </main> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React Router 7 Typegen Route Hydration and Single-Fetch Streaming Boundaries

React Router 7 Typegen Route Hydration and Single-Fetch Streaming Boundaries defines an industrial-grade behavioral standard for frontend engineering. Enforces strict typegen module contracts, turbo-stream single-fetch data boundaries, and safe clientLoader hydration patterns in React Router 7 framework mode. Prevents hydration mismatches, double data fetching during hydration, and deprecated v2 defer/json abstractions. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Using deprecated json()/defer() helpers and uncoordinated clientLoaders causing hydration waterfall flashes Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Using deprecated json()/defer() helpers and uncoordinated clientLoaders causing hydration waterfall flashes	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS import route types directly from the collocated typegen artifacts (e.g., `./+types/[route-file]`) for Route.LoaderArgs, Route.ComponentProps, and Route.ActionArgs.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.