SolidStart 1.0 Server Functions (server$) & Async Reactive Boundaries

--- description: SolidStart 1.0 Server Functions (server$) & Async Reactive Boundaries - Enforces strict isolation between SolidJS fine-grained client reactivity and SolidStart 1.0 server$ RPC serialization boundaries. Prohibits naked server invocations inside synchronous tracking scopes, accidental signal closure leaks into server execution contexts, and unhandled async streaming states across client-server transitions. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/solidstart-server-functions-async-boundaries-standard" --- # SolidStart 1.0 Server Functions (server$) & Async Reactive Boundaries > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Executing naked server$ RPCs inside reactive tracking scopes and passing reactive accessors into serialized payloads. ## System Constraints You are a Principal Engineer enforcing SolidStart 1.0 architectural invariants. You must prevent serialization leakage, infinite refetch loops in tracking scopes, and unhandled async boundary crashes when interacting with server$ functions, createAsync, and Vinxi server RPCs. ## Strict Guidelines - Engineers MUST ALWAYS wrap data-fetching server$ calls with query() or cache() and consume them via createAsync() to ensure proper deduplication, SSR hydration transfer, and fine-grained tracking isolation. - Engineers MUST NOT pass raw signal getters, reactive proxies, or non-serializable instances (e.g., DOM references, class prototypes) into server$ RPC argument lists; unwrapping MUST occur explicitly via accessor invocation before passing values across the wire. - Engineers MUST NEVER invoke naked server$ calls directly inside tracking scopes (createEffect, createMemo, or root component rendering bodies) without gating or using SolidStart actions; doing so triggers cascade network loops. - Components consuming async server resources MUST ALWAYS be encapsulated within paired <Suspense> and <ErrorBoundary> boundaries to support streaming SSR and isolate network rejection states without breaking fine-grained client hydration. - Mutations targeting server$ MUST use the action() primitive or useSubmission() to ensure automatic route revalidation and safe optimistic UI updates across RPC boundaries. ## Bad vs Good Implementations ### Data Fetching with server$ and createAsync vs. Naked RPC in Tracking Scope #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Invoking server$ inside createEffect bypasses SolidStart's SSR serialization cache, breaks streaming SSR hydration, and leads to client-side data waterfalls or layout shifts without Suspense coordination. ```typescript import { createSignal, createEffect } from 'solid-js'; import { server$ } from '@solidjs/start/server'; const fetchUserProfile = server$(async (userId: string) => { const db = await import('~/server/db'); return db.getUser(userId); }); export default function Profile() { const [userId] = createSignal('usr_123'); const [data, setData] = createSignal<any>(null); // ANTI-PATTERN: Direct invocation of server$ inside createEffect creates // duplicate server requests, bypasses hydration serialization cache, and causes watermarked waterfalls. createEffect(async () => { const user = await fetchUserProfile(userId()); // Passing accessor call in tracking scope manually setData(user); }); return <div>{data()?.name}</div>; } ``` #### Production Standard (Correct) > **Standard**: Using query() with 'use server' and consuming it through createAsync() preserves reactive tracking dependencies cleanly, enables full SSR streaming hydration, and coordinates gracefully with <Suspense>. ```typescript import { createSignal, Suspense, ErrorBoundary } from 'solid-js'; import { query, createAsync } from '@solidjs/router'; // GOOD: Encapsulated server function within query cache for SSR serialization const getUserProfile = query(async (userId: string) => { 'use server'; const db = await import('~/server/db'); return db.getUser(userId); }, 'users.getProfile'); export default function Profile() { const [userId] = createSignal('usr_123'); // createAsync tracks accessor reactive dependencies and integrates with Suspense/SSR const user = createAsync(() => getUserProfile(userId())); return ( <ErrorBoundary fallback={(err) => <div>Error: {err.message}</div>}> <Suspense fallback={<div>Loading profile...</div>}> <div>{user()?.name}</div> </Suspense> </ErrorBoundary> ); } ``` ### Server Actions and Mutation Boundaries vs. Direct RPC Calls #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Directly calling server$ RPCs for mutations forces manual synchronization, bypasses router-level cache invalidation, and fails to handle race conditions during concurrent submissions. ```typescript import { createSignal } from 'solid-js'; import { server$ } from '@solidjs/start/server'; const updateUserStatus = server$(async (payload: { id: string; active: boolean }) => { const db = await import('~/server/db'); return db.updateStatus(payload.id, payload.active); }); export function StatusToggle(props: { id: string }) { const [loading, setLoading] = createSignal(false); // ANTI-PATTERN: Direct RPC execution bypasses SolidStart route invalidation; // manual error and pending state management is vulnerable to race conditions. const handleToggle = async () => { setLoading(true); await updateUserStatus({ id: props.id, active: true }); setLoading(false); }; return <button disabled={loading()} onClick={handleToggle}>Activate</button>; } ``` #### Production Standard (Correct) > **Standard**: SolidStart action() paired with useSubmission handles progressive enhancement, automatically triggers router invalidations to refetch active queries, and manages pending states idempotently. ```typescript import { action, useSubmission } from '@solidjs/router'; // GOOD: Define action with 'use server' to automate cache invalidation const updateStatusAction = action(async (formData: FormData) => { 'use server'; const id = String(formData.get('id')); const active = formData.get('active') === 'true'; const db = await import('~/server/db'); return db.updateStatus(id, active); }, 'users.updateStatus'); export function StatusToggle(props: { id: string }) { const submission = useSubmission(updateStatusAction); return ( <form action={updateStatusAction} method="post"> <input type="hidden" name="id" value={props.id} /> <input type="hidden" name="active" value="true" /> <button type="submit" disabled={submission.pending}> {submission.pending ? 'Updating...' : 'Activate'} </button> </form> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SolidStart 1.0 Server Functions (server$) & Async Reactive Boundaries

SolidStart 1.0 Server Functions (server$) & Async Reactive Boundaries defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between SolidJS fine-grained client reactivity and SolidStart 1.0 server$ RPC serialization boundaries. Prohibits naked server invocations inside synchronous tracking scopes, accidental signal closure leaks into server execution contexts, and unhandled async streaming states across client-server transitions. 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: Executing naked server$ RPCs inside reactive tracking scopes and passing reactive accessors into serialized payloads. 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	Executing naked server$ RPCs inside reactive tracking scopes and passing reactive accessors into serialized payloads.	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 wrap data-fetching server$ calls with query() or cache() and consume them via createAsync() to ensure proper deduplication, SSR hydration transfer, and fine-grained tracking isolation.

Engineers MUST ALWAYS wrap data-fetching server$ calls with query() or cache() and consume them via createAsync() to ensure proper deduplication, SSR hydration transfer, and fine-grained tracking isolation.

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.