Nuxt

Nitroship manages Nuxt’s Nitro Node server and its client assets, or publishes a generated site without compute.

Detection and build outputCopy Anchor Link

• Detection: nuxt in the root package.json. Keep a build script, normally nuxt build.
• Server builds set NITRO_PRESET=node-server. The .output bundle starts with node server/index.mjs; .output/public is published to the CDN.
• If the build script runs nuxt generate or nuxi generate, the preset publishes .output/public as a static site. No compute region is needed for this mode.

DeployCopy Anchor Link

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

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

Nuxt ImageCopy Anchor Link

For /_ipx/... image URLs on a generated static site, enable IPX transformation. Remote images must be on the allowlist; see Image optimization. This does not replace Nuxt server features.

{"images": {"protocol": "ipx"}}

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.