TanStack Start best practices

Use when working with TanStack Start (full-stack React, SSR, server functions, Nitro/Vite-style apps).

Mental model

• Start coordinates routing, SSR, data loading, and server functions. Prefer framework-native patterns over bolting on parallel systems.
• Distinguish server-only code (secrets, DB, filesystem) from client code; never import server-only modules into client bundles.

Routes and files

• Use the file-based route tree the project already has; match existing naming (route.tsx, layouts, pathless layouts).
• Loaders fetch data needed for the route; keep them focused and parallel-friendly.
• Return or throw in ways the framework expects for errors and redirects (typed errors, error boundaries).

Server functions