start-deployment
/start-deployment
Pomaga budować i wdrażać aplikację TanStack Start na Cloudflare, Netlify, Vercel, Node lub Bun, z prerenderowaniem i zmiennymi środowiskowymi.
- Autor
- fusengine ↗
- Repozytorium
- agents ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pomaga budować i wdrażać aplikację TanStack Start na Cloudflare, Netlify, Vercel, Node lub Bun, z prerenderowaniem i zmiennymi środowiskowymi.
Oryginalny opis (EN)
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.
Jak działa
- Agent Workflow (MANDATORY)
- Overview
- Critical Rules
- Architecture
- Reference Guide
- Best Practices
Podgląd SKILL.md
---
name: start-deployment
description: 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.
versions:
"@tanstack/react-start": "^1"
vite: "^6"
user-invocable: false
references: 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.md
related-skills: nextjs-16, astro-deployment
---
<objective>
Covers 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 }).
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.
</objective>
# TanStack Start — Deployment
## Agent Workflow (MANDATORY)
Before ANY implementation, spawn in parallel:
1. **fuse-ai-pilot:explore-codebase** — read `vite.config.ts`, `package.json` scripts, existing adapter/wrangler config
2. **fuse-ai-pilot:research-expert** — verify adapter setup via Context7 `/websites/tanstack_start_framework_react`
3. **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 / Render / Node / Docker / Bun / Railway** | Nitro layer (`nitro/vite`), `.output/server/index.mjs` |
| **Static** | `tanstackStart({ prerender: { enabled: true, crawlLinks }, pages: [{ path }] })` |
Start builds with **Vite** (or Rsbuild). Most hosts go through **Nitro**, an agnostic deploy layer; Cloudflare and Netlify have dedicated Vite plugins.
---
## Critical Rules
1. **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.
2. **Cloudflare plugin order** — `cloudflare({ viteEnvironment: { name: 'ssr' } })` before `tanstackStart()` in the plugins array.
3. **Match `start` to the build** — Nitro output starts with `node .output/server/index.mjs`; Cloudflare uses `wrangler deploy` (no `node` start).
4. **React 19 for Bun** — pin `react`/`react-dom` to `>= 19` when deploying on Bun.
5. **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](references/templates/vite-config-adapters.md) for every adapter config
---
## Reference Guide
### Concepts
| Topic | Reference | Load when |
|-------|-----------|-----------|
| **Build & adapters** | [build-and-adapters.md](references/build-and-adapters.md) | Choosing/configuring a host (Nitro, Vercel, Node, Bun, Railway, Netlify) |
| **Cloudflare** | [cloudflare.md](references/cloudflare.md) | Deploying to Cloudflare Workers |
| **Prerendering** | [prerendering.md](references/prerendering.md) | Generating static HTML at build time |
| **Env & checklist** | [env-and-checklist.md](references/env-and-checklist.md) | Production env vars + pre-deploy checklist |
### Templates
| Template | When to Use |
|----------|-------------|
| [vite-config-adapters.md](references/templates/vite-config-adapters.md) | Full `vite.config.ts` per target + prerender |
| [cloudflare-deploy.md](references/templates/cloudflare-deploy.md) | Complete Cloudflare Workers setup |
---
## Best Practices
### DO
- Confirm the official partner list (Netlify, Render, Cloudflare, Vercel, Railway, Lovable) 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`
Pliki w paczce (7)
- SKILL.md 5 KB
- references/build-and-adapters.md 3 KB
- references/cloudflare.md 3 KB
- references/env-and-checklist.md 3 KB
- references/prerendering.md 3 KB
- references/templates/cloudflare-deploy.md 3 KB
- references/templates/vite-config-adapters.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie start-deployment.
Migawka bazy z 13.11.2026 · wersja paczki 99618188ef56 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100tanstack-start
Podpowiada dobre praktyki TanStack Start: server functions z createServerFn, SSR ze streamingiem, API routes, app.config.ts oraz wdrożenie na Node, Vercel, Netlify, Bun i Cloudflare. - 90astro-deployment
Prowadzi wdrożenie aplikacji Astro 7 na Cloudflare, Vercel, Netlify lub Node.js: adaptery, wzorce ISR i edge middleware. - 100release
Przygotowuje lokalną konfigurację wdrożenia dla Cloudflare, Render, Vercel lub Netlify i sprawdza build, start i health check bez wdrażania. - 100netlify
Pomaga wdrażać i obsługiwać stronę na Netlify: netlify.toml, Functions i Edge Functions, przekierowania, nagłówki, zmienne środowiskowe per kontekst i Netlify CLI. - 100bun-cloudflare-workers
Wspiera budowanie i wdrażanie aplikacji na Cloudflare Workers z użyciem Bun: wrangler, wdrożenie brzegowe i przenoszenie projektu Bun na Workers. - 95netlify-frameworks
Pomaga wdrażać frameworki webowe na Netlify, takie jak Astro, Next.js, Nuxt czy SvelteKit, i diagnozuje ich integrację.