start-server-routes

Topics in the source

• TanStack Start Server Routes
• Agent Workflow (MANDATORY)
• Critical Rules (read first)
• Overview
• Architecture
• Reference Guide
• Concepts
• Templates

Covers server routes — raw HTTP endpoints defined alongside app routes in src/routes/ using the server property on createFileRoute (from @tanstack/react-router), returning standard Response objects. Targets @tanstack/react-start v1.169.5. Documents the handler context ({ request, params, context, pathname, next }), dynamic ($id) and splat ($) params from the file name, per-handler middleware via createHandlers versus route-wide server.middleware, and how the same file can serve as both a UI route (component) and an API route (server) at once. Critical rules: choose a server route over a server function when the endpoint must be callable from outside the app (webhooks, public REST, cross-origin) — see references/vs-server-functions.md for the decision; exactly one handler file may resolve to a given route path (routes/users.ts, routes/users/index.ts, and routes/users.index.ts all collide on /users); always await request.json()/.text()/.formData(); and handlers must return a Response (or Promise ). Includes a full REST-resource template with params and middleware. Do NOT use this skill for internal type-safe RPC callable only from your own app (use start-server-functions), for reusab

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