start-execution-model

Topics in the source

• TanStack Start Execution Model
• Agent Workflow (MANDATORY)
• The Boundary APIs at a Glance
• The One Gotcha to Remember
• Reference Guide
• Decision Framework
• Forbidden

Covers TanStack Start's execution model — where code actually runs, described as the single most important concept in Start and the #1 source of AI-generated bugs. Targets @tanstack/react-start v1.169.5. Every module is isomorphic by default: it runs in BOTH server and client bundles, and route loaders run on both server (SSR) and client (navigation) — so DB access, filesystem, and secrets must live inside createServerFn or createServerOnlyFn, never a bare loader or module scope. process.env must be read per request, not at module scope, because module-level reads can leak into the client bundle and are undefined on edge runtimes that inject env at request time. VITE/PUBLIC-prefixed vars are exposed to the client, so server secrets must never carry that prefix. Documents every environment-boundary API at a glance — createServerFn, createServerOnlyFn, createClientOnlyFn, createIsomorphicFn, , useHydrated(), and the server-only/client-only import markers — with a decision framework for which to use and complete copy-paste boundary examples. Do NOT use this skill for initial project setup (use start-core) or for file/directory SOLID organization (use solid-tanstack-start). Understandi

This is an excerpt. Refer to the complete source and its current requirements.