Deploy
Ship your SSR app anywhere — one WinterCG fetch handler plus build adapters for Cloudflare Workers, Vercel and Netlify, and documented Node, Deno and Bun entries.
One fetch handler
createFetchHandler is the whole runtime story — a WinterCG Request → Response handler that runs unchanged on Node, workerd, Deno, Bun and the edge runtimes.
You own the entry
src/entry.<platform>.ts is scaffolded once and never overwritten — the static → server functions → document composition stays a readable file in your repo.
Adapters are build glue
Each adapter rides the public SigxAdapter seam in @sigx/vite — export conditions, bundling mode and platform output generation. No privileged access, no runtime lock-in.
Platform-native statics
Static assets are served by each platform’s own tier — Workers assets, the Build Output filesystem route, Netlify’s CDN — before your code ever runs.
Deploy with their CLI
vite build --app, then wrangler deploy, vercel deploy --prebuilt or netlify deploy --prod — the output sits on disk, inspectable before it ships.
No package for Deno & Bun
A SigxAdapter is a plain object — Deno and Bun deploy from a few documented lines of vite config, no adapter package required.
Deploy is a collection — there's no single install. Add the package you need from the list below.