Build once, deploy to many hosts
Build your app into one folder, then pick where it runs with a Nitro preset.
Last page, you wrote pages, endpoints, and middleware. Now ship them.
The router builds on Nitro. Nitro has presets for many hosts. We built one app for a Node server and for Vercel, with no code change.
Pick a host. Then run the build.
Where can one build run?
Pick a host. Then press Run the build and look at the folder it writes.
$ npm run build
Not run yet.
- pages/same for every host
- api/same for every host
- middleware/same for every host
- document.tsrxsame for every host
- vite.config.tssame for every host
- Nothing yet. Press Run the build.
Simplified. We built one app from the full-stack starter both ways: as a Node server, the default, and for Vercel. We changed no file between the two builds. The output lists show the main entries only. Other hosts are untested.
Notice that your files stay the same. Only the output folder changes.
The default: a Node server
npm run build
PORT=3000 node .output/server/index.mjsThe build runs three steps: the browser build, the server build, then Nitro. By default, Nitro builds a Node server. The server reads the PORT variable.
To try the build on your machine, run npm run preview.
What is in .output/
| Path | What it holds |
|---|---|
.output/server/index.mjs |
the server you start |
.output/public/build/ |
the browser code, sent with cache-control: public, max-age=31536000, immutable |
.output/markless/router/types/ |
the route types |
.output/nitro.json |
Nitro build information |
Other hosts with a preset
Nitro reads the preset from the NITRO_PRESET variable. This build writes output for Vercel:
NITRO_PRESET=vercel npm run buildThe output goes to .vercel/output/, with static/ and functions/ folders. The Markless website deploys this way.
Nitro has presets for many other hosts. We tested only the default Node server and Vercel with Markless. Treat other presets as untested.
Next: Which options can you change in vite.config.ts? Configuration →