Covers production env-var handling (read process.env per request, never at module scope — Cloudflare injects env at request time so module-level reads are undefined on the edge), plugin ordering (cloudflare() before tanstackStart()), matching start scripts to the build output, React 19 pinning for Bun, and prerendering limits (dynamic $id routes, layout _ routes, and component-less routes are skipped unless linked via crawlLinks).
Includes full vite.config.ts templates per adapter and a complete Cloudflare Workers deploy template, plus a production checklist.
Do NOT use this skill for app data/auth logic (see start-routing-data / start-auth) or for generic Vite config unrelated to Start.
TanStack Start — Deployment
Agent Workflow (MANDATORY)
Before ANY implementation, spawn in parallel:
- fuse-ai-pilot:explore-codebase — read
vite.config.ts, package.json scripts, existing adapter/wrangler config
- fuse-ai-pilot:research-expert — verify adapter setup via Context7
/websites/tanstack_start_framework_react
- mcp__context7__query-docs — confirm
tanstackStart plugin + adapter options for the target host
After implementation, run fuse-ai-pilot:sniper.
Overview
| Target |
Setup |
| Cloudflare Workers ⭐ |
@cloudflare/vite-plugin (viteEnvironment: { name: 'ssr' }) + wrangler.jsonc |
| Netlify ⭐ |
@netlify/vite-plugin-tanstack-start |
| Vercel / Node / Docker / Bun / Railway |
Nitro layer (nitro/vite), .output/server/index.mjs |
| Static |
tanstackStart({ prerender: { routes, crawlLinks } }) |
Start builds with Vite (or Rsbuild). Most hosts go through Nitro, an agnostic deploy layer; Cloudflare and Netlify have dedicated Vite plugins.
Critical Rules
- Read env per request —
process.env.X inside handlers, NEVER at module scope; Cloudflare injects env at request time, so module reads are undefined on the edge.
- Cloudflare plugin order —
cloudflare({ viteEnvironment: { name: 'ssr' } }) before tanstackStart() in the plugins array.
- Match
start to the build — Nitro output starts with node .output/server/index.mjs; Cloudflare uses wrangler deploy (no node start).
- React 19 for Bun — pin
react/react-dom to >= 19 when deploying on Bun.
- Prerender excludes dynamics — param routes (
$id), layout routes (_), and component-less routes are skipped unless linked with crawlLinks.
Architecture
vite.config.ts # tanstackStart() + host adapter (cloudflare / netlify / nitro)
wrangler.jsonc # Cloudflare only — main: @tanstack/react-start/server-entry
package.json # scripts differ per target (deploy vs start)
.output/server/ # Nitro build output (Node/Vercel/Bun/Railway)
→ See vite-config-adapters.md for every adapter config
Reference Guide
Concepts
| Topic |
Reference |
Load when |
| Build & adapters |
build-and-adapters.md |
Choosing/configuring a host (Nitro, Vercel, Node, Bun, Railway, Netlify) |
| Cloudflare |
cloudflare.md |
Deploying to Cloudflare Workers |
| Prerendering |
prerendering.md |
Generating static HTML at build time |
| Env & checklist |
env-and-checklist.md |
Production env vars + pre-deploy checklist |
Templates
| Template |
When to Use |
| vite-config-adapters.md |
Full vite.config.ts per target + prerender |
| cloudflare-deploy.md |
Complete Cloudflare Workers setup |
Best Practices
DO
- Confirm the official partner list (Cloudflare, Netlify, Railway) before hand-rolling config
- Keep secrets in the host's env store; read them per request
- Prerender marketing/blog routes; keep dynamic/auth routes SSR
DON'T
- Read
process.env at import time (edge = undefined; bundle leak)
- Mix a Nitro
node start script with a Cloudflare build
- Expect
$param routes to prerender without crawlLinks
1---2name: start-deployment3description: Use when building or deploying a TanStack Start app — Cloudflare, Netlify, Vercel/Node/Bun, prerendering, or env vars. Do NOT use for app logic or generic Vite config.4versions:5 "@tanstack/react-start": "^1"6 vite: "^6"7user-invocable: false8references: references/build-and-adapters.md, references/cloudflare.md, references/prerendering.md, references/env-and-checklist.md, references/templates/vite-config-adapters.md, references/templates/cloudflare-deploy.md9related-skills: nextjs-16, astro-deployment10metadata:11 source: https://skillmd.com/skills/fusengine/start-deployment12---1314<objective>15Covers building and deploying TanStack Start apps across hosting targets: dedicated Vite plugins for Cloudflare Workers (@cloudflare/vite-plugin + wrangler.jsonc) and Netlify (@netlify/vite-plugin-tanstack-start), the Nitro layer for Vercel/Node/Docker/Bun/Railway (.output/server/index.mjs), and static prerendering via tanstackStart({ prerender }).1617Covers production env-var handling (read process.env per request, never at module scope — Cloudflare injects env at request time so module-level reads are undefined on the edge), plugin ordering (cloudflare() before tanstackStart()), matching start scripts to the build output, React 19 pinning for Bun, and prerendering limits (dynamic $id routes, layout _ routes, and component-less routes are skipped unless linked via crawlLinks).1819Includes full vite.config.ts templates per adapter and a complete Cloudflare Workers deploy template, plus a production checklist.2021Do NOT use this skill for app data/auth logic (see start-routing-data / start-auth) or for generic Vite config unrelated to Start.22</objective>2324# TanStack Start — Deployment2526## Agent Workflow (MANDATORY)2728Before ANY implementation, spawn in parallel:29301. **fuse-ai-pilot:explore-codebase** — read `vite.config.ts`, `package.json` scripts, existing adapter/wrangler config312. **fuse-ai-pilot:research-expert** — verify adapter setup via Context7 `/websites/tanstack_start_framework_react`323. **mcp__context7__query-docs** — confirm `tanstackStart` plugin + adapter options for the target host3334After implementation, run **fuse-ai-pilot:sniper**.3536---3738## Overview3940| Target | Setup |41|--------|-------|42| **Cloudflare Workers** ⭐ | `@cloudflare/vite-plugin` (`viteEnvironment: { name: 'ssr' }`) + `wrangler.jsonc` |43| **Netlify** ⭐ | `@netlify/vite-plugin-tanstack-start` |44| **Vercel / Node / Docker / Bun / Railway** | Nitro layer (`nitro/vite`), `.output/server/index.mjs` |45| **Static** | `tanstackStart({ prerender: { routes, crawlLinks } })` |4647Start builds with **Vite** (or Rsbuild). Most hosts go through **Nitro**, an agnostic deploy layer; Cloudflare and Netlify have dedicated Vite plugins.4849---5051## Critical Rules52531. **Read env per request** — `process.env.X` inside handlers, NEVER at module scope; Cloudflare injects env at request time, so module reads are `undefined` on the edge.542. **Cloudflare plugin order** — `cloudflare({ viteEnvironment: { name: 'ssr' } })` before `tanstackStart()` in the plugins array.553. **Match `start` to the build** — Nitro output starts with `node .output/server/index.mjs`; Cloudflare uses `wrangler deploy` (no `node` start).564. **React 19 for Bun** — pin `react`/`react-dom` to `>= 19` when deploying on Bun.575. **Prerender excludes dynamics** — param routes (`$id`), layout routes (`_`), and component-less routes are skipped unless linked with `crawlLinks`.5859---6061## Architecture6263```64vite.config.ts # tanstackStart() + host adapter (cloudflare / netlify / nitro)65wrangler.jsonc # Cloudflare only — main: @tanstack/react-start/server-entry66package.json # scripts differ per target (deploy vs start)67.output/server/ # Nitro build output (Node/Vercel/Bun/Railway)68```6970→ See [vite-config-adapters.md](references/templates/vite-config-adapters.md) for every adapter config7172---7374## Reference Guide7576### Concepts7778| Topic | Reference | Load when |79|-------|-----------|-----------|80| **Build & adapters** | [build-and-adapters.md](references/build-and-adapters.md) | Choosing/configuring a host (Nitro, Vercel, Node, Bun, Railway, Netlify) |81| **Cloudflare** | [cloudflare.md](references/cloudflare.md) | Deploying to Cloudflare Workers |82| **Prerendering** | [prerendering.md](references/prerendering.md) | Generating static HTML at build time |83| **Env & checklist** | [env-and-checklist.md](references/env-and-checklist.md) | Production env vars + pre-deploy checklist |8485### Templates8687| Template | When to Use |88|----------|-------------|89| [vite-config-adapters.md](references/templates/vite-config-adapters.md) | Full `vite.config.ts` per target + prerender |90| [cloudflare-deploy.md](references/templates/cloudflare-deploy.md) | Complete Cloudflare Workers setup |9192---9394## Best Practices9596### DO97- Confirm the official partner list (Cloudflare, Netlify, Railway) before hand-rolling config98- Keep secrets in the host's env store; read them per request99- Prerender marketing/blog routes; keep dynamic/auth routes SSR100101### DON'T102- Read `process.env` at import time (edge = undefined; bundle leak)103- Mix a Nitro `node` start script with a Cloudflare build104- Expect `$param` routes to prerender without `crawlLinks`