Nuxt 4 Nitro Server Engine, Directory Restructure, and SSR State Isolation

--- description: Nuxt 4 Nitro Server Engine, Directory Restructure, and SSR State Isolation - Enforces strict boundary isolation between Nuxt 4's app/ layer, server/ Nitro runtime, and shared/ utilities. Prohibits global mutable state in server routes and shared modules that trigger cross-request state pollution, and prevents client-server reactivity leakage during SSR hydration. globs: app/**/*.{ts,vue}, server/**/*.{ts,js}, shared/**/*.{ts,js}, nuxt.config.ts alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/nuxt4-nitro-shared-ssr-state-isolation-standard" --- # Nuxt 4 Nitro Server Engine, Directory Restructure, and SSR State Isolation > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Global Module-Level State in Nitro Handlers and Shared Modules Causing Cross-Request Data Leaks and Hydration Mismatches ## System Constraints You are a Principal Software Architect enforcing Nuxt 4 architectural boundaries, Nitro v2 server routing rules, and strict SSR state isolation. Enforce zero global mutable state in server/ and shared/, mandate app/ directory layout compliance, and eliminate hydration mismatches caused by un-isolated shared references. ## Strict Guidelines - Engineers MUST ALWAYS isolate all Vue-layer code inside the 'app/' directory (e.g., app/components, app/composables, app/pages) conforming to Nuxt 4 directory structures. - Engineers MUST NOT declare mutable module-level variables (e.g., let currentSession, const cache = new Map()) in 'server/' handlers or 'shared/' modules because Node/Edge runtimes reuse module instances across concurrent requests. - Engineers MUST use 'event.context' or scoped context handlers (e.g., unstorage with scoped keys or AsyncLocalStorage via unenv) for any per-request data passing in Nitro server routes. - Engineers MUST use 'useState()' inside 'app/composables' for SSR-friendly, request-isolated reactive state and NEVER initialize global reactive 'ref()' or 'reactive()' singletons at the root module scope. - Engineers MUST keep 'shared/' code strictly pure and functional, containing only type definitions, deterministic pure validation functions, or schema parsers (e.g., Zod) with zero runtime state or platform-specific APIs. - Components NEVER directly invoke Nitro-internal utilities or access server environment secrets ('useRuntimeConfig().serverSecret' must remain inaccessible to client bundle contexts). ## Bad vs Good Implementations ### Cross-Request State Leakage in Nitro Handler vs. Scoped Event Context #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: In persistent server environments (Node.js, long-lived serverless runtimes), module-level variables persist across invocations. Storing request-specific data in 'cachedUserProfile' leaks sensitive user data across concurrent users. ```typescript // server/api/user/profile.ts // ANTI-PATTERN: Module-scoped state shared across concurrent requests let cachedUserProfile: Record<string, unknown> | null = null; export default defineEventHandler(async (event) => { const authHeader = getRequestHeader(event, 'authorization'); if (authHeader) { cachedUserProfile = await fetchUserProfile(authHeader); } // Cross-tenant data leak: another concurrent request will read this polluted variable return { user: cachedUserProfile }; }); ``` #### Production Standard (Correct) > **Standard**: Attaching request-specific metadata to 'event.context' ensures lifecycle isolation. The data is garbage collected once the response completes and cannot leak across requests. ```typescript // server/api/user/profile.ts // PRODUCTION FIX: Pure, request-scoped context attached to H3Event export default defineEventHandler(async (event) => { const authHeader = getRequestHeader(event, 'authorization'); if (!authHeader) { throw createError({ statusCode: 401, statusMessage: 'Unauthorized' }); } // Scoped strictly to this event lifecycle event.context.user = await fetchUserProfile(authHeader); return { user: event.context.user }; }); ``` ### Nuxt 4 Shared Directory State vs. Pure Schema/Type Isolation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Importing Vue reactivity into shared utilities creates runtime dependency friction inside Nitro and leaks cross-request tenant identity across SSR runs. ```typescript // shared/utils/session.ts // ANTI-PATTERN: Shared stateful singleton imported into both app/ and server/ import { ref } from 'vue'; // Breaks Nitro runtime when bundling without Vue export const activeTenant = ref<string>('default'); export function setTenant(tenantId: string) { activeTenant.value = tenantId; } ``` #### Production Standard (Correct) > **Standard**: The 'shared/' directory remains pure and stateless. Types and pure validation functions are safely shared across 'app/' and 'server/' without memory leaks or framework binding issues. ```typescript // shared/types/tenant.ts // PRODUCTION FIX: Pure stateless TypeScript schemas and utility contracts import { z } from 'zod'; export const TenantConfigSchema = z.object({ id: z.string().uuid(), name: z.string().min(1), tier: z.enum(['standard', 'enterprise']) }); export type TenantConfig = z.infer<typeof TenantConfigSchema>; export function validateTenantPayload(payload: unknown): TenantConfig { return TenantConfigSchema.parse(payload); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Nuxt 4 Nitro Server Engine, Directory Restructure, and SSR State Isolation

Nuxt 4 Nitro Server Engine, Directory Restructure, and SSR State Isolation defines an industrial-grade behavioral standard for frontend engineering. Enforces strict boundary isolation between Nuxt 4's app/ layer, server/ Nitro runtime, and shared/ utilities. Prohibits global mutable state in server routes and shared modules that trigger cross-request state pollution, and prevents client-server reactivity leakage during SSR hydration. 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: Global Module-Level State in Nitro Handlers and Shared Modules Causing Cross-Request Data Leaks and Hydration Mismatches 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	Global Module-Level State in Nitro Handlers and Shared Modules Causing Cross-Request Data Leaks and Hydration Mismatches	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 isolate all Vue-layer code inside the 'app/' directory (e.g., app/components, app/composables, app/pages) conforming to Nuxt 4 directory structures.

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.