Deploy by framework

TanStack Start

Deploy TanStack Start for React or Solid with Nitro’s Node adapter.

Nitroship manages Nitro-backed TanStack Start applications for React and Solid.

Detection and build output

  • Detection: @tanstack/react-start or @tanstack/solid-start in package.json. Keep the Vite build script.
  • Install nitro and enable nitro/vite in the project’s Vite configuration alongside the Start plugin. A server build without this deployment adapter is not a runnable HTTP server.
  • Nitroship sets NITRO_PRESET=node-server, packages the self-contained .output directory, and starts node server/index.mjs from that bundle. .output/public is served from the CDN.
  • Other deployment adapters, edge runtimes, and custom output layouts are outside this preset’s contract.

Deploy

Install the CLI

curl -fsSL https://nitroship.co/install.sh | bash
ntro login

Already installed? Skip ahead. Full options, PATH setup, and updates: Install the CLI.

nitroship.json
{
  "build": {"framework": "tanstack-start"},
  "compute": {"regions": ["kr-icn"]}
}

Setting build.framework skips detection and uses this preset, even if your project root has a Dockerfile. It can't be combined with build.dockerfile. Without it, Nitroship detects the build as described in How Nitroship chooses a build.

ntro apps create my-tanstack-start-app
ntro deploy . --prod

After installing dependencies, you can also build locally with ntro deploy . --prod --local. After deployment, open static assets and a server route at the URL printed by the CLI.

Limits and custom setups

Server deployments need a compute region. Your server must listen on 0.0.0.0:$PORT (default 3000). Client assets come from the CDN, and a single Node server handles all SSR and API requests; routes aren't split into separate functions the way Next.js routes are.

Nitroship does not automatically run migrations, queue workers, or schedulers. Run migrations in CI or locally; see Scheduled jobs for periodic work. Store uploads in S3 or other object storage, and configure secrets through Environment variables.

For adapters or output layouts outside this contract, use your own Dockerfile. Remove build.framework and define installation, build, and startup in the Dockerfile.

On this page