docs(start): Add Railway instructions (#4910)

ianjmacintosh · web-flow · commit 741821b2d248 · 2025-09-04T21:49:49.000-05:00
I was puzzled why Railway wasn't starting a server, then realized
TanStack Start doesn't define the start command by default
diff --git a/docs/start/framework/react/hosting.md b/docs/start/framework/react/hosting.md
@@ -36,6 +36,7 @@ When a TanStack Start application is being deployed, the `target` value in the T
 - [`netlify`](#netlify): Deploy to Netlify
 - [`vercel`](#vercel): Deploy to Vercel
 - [`cloudflare-pages`](#cloudflare-pages): Deploy to Cloudflare Pages
+- [`railway`](#railway): Deploy to Railway
 - [`node-server`](#nodejs): Deploy to a Node.js server
 - [`bun`](#bun): Deploy to a Bun server
 - ... and more to come!
@@ -108,6 +109,41 @@ directory = "./.output/public"
 
 Deploy your application to Cloudflare Workers using their one-click deployment process, and you're ready to go!
 
+### Railway
+
+Railway automatically detects Build and Start commands when building and deploying to a service.
+
+Set the `target` value to `node-server` in your `vite.config.ts` file.
+
+```ts
+// vite.config.ts
+import { tanstackStart } from '@tanstack/react-start/plugin/vite'
+import { defineConfig } from 'vite'
+
+export default defineConfig({
+  plugins: [tanstackStart({ target: 'node-server' })],
+})
+```
+
+Ensure `build` and `start` npm scripts are present in your `package.json` file:
+
+```json
+    "build": "vite build",
+    "start": "node .output/server/index.mjs"
+```
+
+Then you can run the following command to build your application:
+
+```sh
+npm run build
+```
+
+You can start your application by running:
+
+```sh
+npm run start
+```
+
 ### Node.js
 
 Set the `target` value to `node-server` in your `vite.config.ts` file.
