SolidStart 1.0 Server Functions (server$) and Async Boundary Architecture

--- description: SolidStart 1.0 Server Functions (server$) and Async Boundary Architecture - Enforces strict isolation between client-side reactive signal scopes and Vinxi-compiled server$ RPC functions in SolidStart 1.0. Guarantees that async data pipelines crossing the network boundary are encapsulated in serializable contracts, driven through createAsync/query primitives, and guarded by explicit Suspense and ErrorBoundary components to eliminate hydration mismatch and stale closure panics. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/solidstart-1-server-functions-async-boundaries" --- # SolidStart 1.0 Server Functions (server$) and Async Boundary Architecture > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Leaking Reactive Signal Accessors into server$ Closures and Unbounded Async Execution Without Suspense ## System Constraints You are a Principal Engineer enforcing SolidStart 1.0 Server Functions & Async Boundaries. Mandate complete lexical isolation between client-side Solid signals and server-extracted closures (server$), enforce strict JSON/Seroval serialization across network boundaries, and ensure all asynchronous reads are routed via createAsync wrapped by Suspense boundaries. ## Strict Guidelines - Engineers MUST ALWAYS pass client reactive values as explicit, serializable primitive or plain-object parameters into server$ or query functions rather than closing over signal accessors. - Engineers MUST ALWAYS wrap components that read createAsync resources in <Suspense> and <ErrorBoundary> primitives to maintain deterministic streaming hydration. - Engineers MUST NOT pass non-serializable references (such as function callbacks, active signal accessors, DOM elements, or class instances with methods) to server$ RPCs. - Code SHOULD define reusable data loaders using @solidjs/router query() or action() with unique cache keys rather than raw, ad-hoc server$ calls directly inside client components. - Components NEVER execute raw asynchronous side-effects directly inside createComputed or createRenderEffect; asynchronous updates must trigger through actions, transitions, or explicit event handlers. ## Bad vs Good Implementations ### Client Signal Leakage into server$ vs. Serializable Query with createAsync #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Vinxi splits server$ functions into distinct server bundles. Capturing userId() inside the closure causes compile-time serialization errors or runtime ReferenceErrors on the server. Omitting createAsync and Suspense bypasses Solid's streaming coordination, causing hydration mismatches. ```typescript import { createSignal } from "solid-js"; import { server$ } from "@solidjs/start/server"; import { db } from "~/server/db"; export default function UserProfile() { const [userId, setUserId] = createSignal("usr_101"); // ANTI-PATTERN: Capturing client-side signal accessor inside server$ closure. // Vinxi extracts this function to a server bundle where userId() is undefined or throws. // Missing Suspense boundary leads to SSR hydration mismatches. const fetchUserData = server$(async () => { const id = userId(); // ReferenceError or stale client reference return await db.user.findUnique({ where: { id } }); }); return ( <div> {/* Directly invoking async function without createAsync triggers unhandled promises */} <button onClick={() => fetchUserData()}>Load</button> </div> ); } ``` #### Production Standard (Correct) > **Standard**: The RPC accepts an explicit, serializable string argument. The client-side signal userId() is evaluated in the reactive tracking scope of createAsync, feeding the serializable query function. Explicit Suspense and ErrorBoundary boundaries enable deterministic streaming SSR and hydration. ```typescript import { createSignal, Suspense, ErrorBoundary } from "solid-js"; import { query, createAsync } from "@solidjs/router"; import { db } from "~/server/db"; // GOOD: Define server RPC outside the component with explicit serializable input const getUser = query(async (id: string) => { "use server"; if (!id) return null; return await db.user.findUnique({ where: { id } }); }, "getUser"); export default function UserProfile() { const [userId, setUserId] = createSignal("usr_101"); // Accessor passed reactively into createAsync const userData = createAsync(() => getUser(userId())); return ( <ErrorBoundary fallback={(err) => <p>Failed to load user: {err.message}</p>}> <Suspense fallback={<p>Loading profile...</p>}> <div> <h1>{userData()?.name}</h1> <button onClick={() => setUserId("usr_102")}>Switch User</button> </div> </Suspense> </ErrorBoundary> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SolidStart 1.0 Server Functions (server$) and Async Boundary Architecture

SolidStart 1.0 Server Functions (server$) and Async Boundary Architecture defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between client-side reactive signal scopes and Vinxi-compiled server$ RPC functions in SolidStart 1.0. Guarantees that async data pipelines crossing the network boundary are encapsulated in serializable contracts, driven through createAsync/query primitives, and guarded by explicit Suspense and ErrorBoundary components to eliminate hydration mismatch and stale closure panics. 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 Signal Accessors into server$ Closures and Unbounded Async Execution Without Suspense 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 Signal Accessors into server$ Closures and Unbounded Async Execution Without Suspense	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 client reactive values as explicit, serializable primitive or plain-object parameters into server$ or query functions rather than closing over signal accessors.

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.