Start deployment

Skill fusengine/agents/plugins/tanstack-start-expert/skills/start-deployment

Redefining development through cognitive automation and collaborative agent systems.

Install

npx -y skills add fusengine/agents --skill start-deployment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when: building or deploying a TanStack Start app — Nitro/Vite build, official adapters (Cloudflare Workers, Netlify, Vercel, Node, Bun, Railway), static prerendering (tanstackStart prerender), production env vars, or a deploy checklist. Do NOT use for: app data/auth logic (see start-routing-data / start-auth) or generic Vite config unrelated to Start.

SKILL.md

4.2 KB, 930 tokens by cl100k_base, as published. Nobody here has run it

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