Skip to main content
Use the Vite guide when the project uses TanStack Router or Query in a Vite frontend. For TanStack Start, retain native server routes, loaders and server functions. Run ohmyhost init --dry-run --json. The result identifies the actual framework/runtime, package manager and required capabilities. Resolve concrete unsupported behavior; do not choose a runtime or authentication system from a package name alone. TanStack Start supports the admitted 1.168.26–1.168.49 window. Import tanstackStart from @tanstack/react-start/plugin/vite. Static mode needs prerender.enabled: true and no Cloudflare plugin; edge mode calls cloudflare({ viteEnvironment: { name: "ssr" } }) before tanstackStart(). Use vite build with at most one admitted tsc stage before or after it. Next/TanStack unknown paths return 404. SSR script/style tags receive the request nonce automatically. Attributes, event handlers and later unnonced tags remain blocked. External browser resources/CORS/frames/workers need exact declarations; server HTML can opt into media/microphone. Scheduled work is declared as functions.crons and runs scheduled from the default export of src/ohmyhost/worker.ts, a module the platform bundles outside the TanStack Start build; see Functions and cron.

​
Deploy and verify

Follow the GitHub deployment workflow. Set server credentials through runtime secrets, and configure the exact application-auth callback/logout URLs. After the build, verify rendered pages, client navigation, loaders, server functions and the requested data writes. For isolated environments, verify existing Prod records after promotion rather than copying Dev data across. Application auth · Dev and Prod.