Nitro Server

Nitro is the server engine powering Nuxt, and is also usable standalone for build-once-deploy-anywhere backend development. It abstracts runtime differences behind a consistent H3 event model — write server handlers once, compile to Node.js, Cloudflare Workers, Vercel, AWS Lambda, or Bun without code changes. Auto-imports, file-based routing, and a built-in devtools make it productive. Good for teams that want deployment flexibility without framework lock-in. Confidence is docs-derived.

Server handlers in server/api/*.ts with defineEventHandler(event => {...}). File-based routing: server/api/predict.post.ts handles POST /api/predict. H3 utilities: readBody(event), getQuery(event), sendStream(event, stream). Auto-imports: Nitro auto-imports composables and utils. Build: nitro build outputs a universal .output folder. nitro dev for local dev server.

No Nitro API key — open-source library. Auth is application-level (H3 middleware, JWT verification, cookie/session management). Open-source MIT license (UnJS). No hosted service auth required.

Error handling via createError({statusCode, statusMessage}). H3 event-based design is well-tested across runtimes. Runtime-specific bugs occasionally surface at deployment time — test against target runtime before production. Active GitHub (unjs/nitro). Well-maintained by the UnJS team.

nitro.unjs.io/guide covers installation, routing, deployment targets, configuration, and H3 utilities. Getting started: npx nitropack init, first handler in under 5 minutes. Open-source MIT (GitHub: unjs/nitro). Community via UnJS Discord.