React Router

Nitroship supports React Router framework mode, including server rendering, loaders, and actions. A client-only React Router library app belongs under Vite SPA.

Detection and build outputCopy Anchor Link

• Detection: @react-router/dev in package.json; keep the react-router build script.
• With SSR enabled, react-router-serve build/server/index.js starts the server. build/client goes to the CDN, and production dependencies are included in the server bundle. Put @react-router/serve in dependencies.
• With ssr: false in react-router.config.ts, build/client is deployed as a static SPA with an automatic /index.html fallback. This mode needs no compute region and cannot run server loaders or actions.
• The preset expects the default framework build layout and the standard serve command; use a Dockerfile for a custom server adapter.

DeployCopy Anchor Link

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

{
  "build": {"framework": "react-router"},
  "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-react-router-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.

Static SPA modeCopy Anchor Link

import type { Config } from "@react-router/dev/config";

export default { ssr: false } satisfies Config;

For this mode, the compute block above is unnecessary. Open a nested route directly after deployment to check the SPA fallback.

Limits and custom setupsCopy Anchor Link

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.