SolidStart 1.0 Server Function Serialization and Async Boundary Guardrail

SolidStart 1.0 server$ functions execute exclusively in isolated server runtime environments, severing the lexical JavaScript scope across client and server boundaries. Passing reactive signal accessors, DOM references, or un-serializable objects into server functions corrupts RPC serialization and triggers client hydration divergence. All server function interactions must pass discrete, plain serializable primitives and be mediated via createAsync or cache primitives wrapped in Suspense and ErrorBoundary components.

--- description: SolidStart 1.0 Server Function Serialization and Async Boundary Guardrail - SolidStart 1.0 server$ functions execute exclusively in isolated server runtime environments, severing the lexical JavaScript scope across client and server boundaries. Passing reactive signal accessors, DOM references, or un-serializable objects into server functions corrupts RPC serialization and triggers client hydration divergence. All server function interactions must pass discrete, plain serializable primitives and be mediated via createAsync or cache primitives wrapped in Suspense and ErrorBoundary components. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/solidstart-server-function-boundary-guardrail" --- # SolidStart 1.0 Server Function Serialization and Async Boundary Guardrail > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Leaking Reactive Closures into server$ RPCs and Invoking Server Functions Inside Raw Client Effects ## System Constraints You are a Principal Engineer enforcing strict SolidStart 1.0 server$ RPC architecture and async reactive boundaries. Prevent client-to-server closure leaks, ensure full JSON/SuperJSON-compatible parameter serialization, mandate createAsync/cache integration for data fetching, and enforce proper Suspense and ErrorBoundary wrapping on all async data trees. ## Strict Guidelines - Engineers MUST ALWAYS pass plain, serializable values (primitives, plain objects, arrays) into server$ RPCs; never pass signal accessors, functions, class instances, or DOM handles. - Engineers MUST NOT access client-side reactive variables directly via closure inside server$ bodies, as compilers isolate server$ into distinct network endpoints with empty client lexical scope. - Code SHOULD fetch and bind server$ functions through createAsync() coupled with cache() or createResource() to integrate natively with Solid's fine-grained reactivity and Suspense lifecycle. - Services MUST validate and sanitize all incoming inputs inside server$ functions using runtime schemas (e.g., Valibot, Zod) before performing backend queries or mutations. - Components NEVER invoke server$ RPCs inside createEffect to manually sync state into local signals; doing so bypasses Suspense, causes hydration mismatches, and triggers waterfall re-renders. ## Bad vs Good Implementations ### Invalid Server RPC Closure and Async Tracking vs. Idiomatic SolidStart 1.0 Boundary #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Declaring server$ inside component scopes invites lexical closure leaks of client signals that fail at runtime. Running RPCs directly inside createEffect causes waterfall executions, hydration mismatches, and defeats Solid's concurrent rendering and Suspense orchestration. ```typescript import { createSignal, createEffect } from "solid-js"; import { server$ } from "@solidjs/start/server"; export function UserProfile() { const [userId, setUserId] = createSignal("usr_42"); const [userData, setUserData] = createSignal<any>(null); // CRITICAL BUG: server$ captures lexical scope incorrectly and is invoked // inside a raw createEffect, bypassing Suspense and causing hydration race conditions. createEffect(async () => { const fetchUser = server$(async () => { // Broken: userId is a client-side accessor unreachable across the server boundary const db = await import("~/server/db"); return db.users.findById(userId()); // Throws runtime reference error }); const data = await fetchUser(); setUserData(data); }); return <div>{userData() ? userData().name : "Loading..."}</div>; } ``` #### Production Standard (Correct) > **Standard**: The server function is declared at module scope with explicit input validation. Reactive resolution is cleanly coordinated via createAsync, ensuring deep integration with Vinxi caching, Solid's Suspense, and hydration boundaries without state synchronization waterfalls. ```typescript import { createSignal, Suspense, ErrorBoundary } from "solid-js"; import { createAsync, cache } from "@solidjs/router"; // Correct: Server action isolated at module level with explicit serializable input const fetchUserById = cache(async (id: string) => { "use server"; if (typeof id !== "string" || !id.startsWith("usr_")) { throw new Error("Invalid user identifier"); } const { db } = await import("~/server/db"); const user = await db.users.findById(id); if (!user) throw new Error("User not found"); return { id: user.id, name: user.name }; }, "users.getById"); export function UserProfile() { const [userId] = createSignal("usr_42"); // Explicitly derive async reactive state through createAsync const user = createAsync(() => fetchUserById(userId())); return ( <ErrorBoundary fallback={(err) => <p role="alert">Error: {err.message}</p>}> <Suspense fallback={<p>Loading profile...</p>}> <section> <h2>Profile</h2> <p>{user()?.name}</p> </section> </Suspense> </ErrorBoundary> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SolidStart 1.0 Server Function Serialization and Async Boundary Guardrail

SolidStart 1.0 Server Function Serialization and Async Boundary Guardrail defines an industrial-grade behavioral standard for frontend engineering. SolidStart 1.0 server$ functions execute exclusively in isolated server runtime environments, severing the lexical JavaScript scope across client and server boundaries. Passing reactive signal accessors, DOM references, or un-serializable objects into server functions corrupts RPC serialization and triggers client hydration divergence. All server function interactions must pass discrete, plain serializable primitives and be mediated via createAsync or cache primitives wrapped in Suspense and ErrorBoundary components. 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: Leaking Reactive Closures into server$ RPCs and Invoking Server Functions Inside Raw Client Effects 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	Leaking Reactive Closures into server$ RPCs and Invoking Server Functions Inside Raw Client Effects	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 pass plain, serializable values (primitives, plain objects, arrays) into server$ RPCs

Engineers MUST ALWAYS pass plain, serializable values (primitives, plain objects, arrays) into server$ RPCs; never pass signal accessors, functions, class instances, or DOM handles.

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.