nuxt-server

# Nuxt 5 Server Development Server routes, API patterns, and backend development with Nitro v3. **Use when**: creating server API routes, implementing server middleware, integrating databases (D1, PostgreSQL, Drizzle), handling file uploads, migrating from Nitro v2/h3 v1 to Nitro v3/h3 v2, or building backend logic. ## Quick Reference ### Nuxt 5 Server API Changes (from Nuxt 4) | Area | Nuxt 4 (Nitro v2) | Nuxt 5 (Nitro v3) | |------|-------------------|-------------------| | Package | `nitropack` | `nitro` | | h3 imports | `import { ... } from 'h3'` | `import { ... } from 'nitro/h3'` | | Error creation | `createError({statusCode})` | `new HTTPError({status})` | | Event path | `event.path` | `event.url.pathname` | | Event method | `event.method` | `event.req.method` | | Status code | `event.node.res.statusCode` | `event.res.status` | | Response headers | `setResponseHeader(event, ...)` | `event.res.headers.set(...)` | | Runtime config | `useRuntimeConfig(event)` | `useRuntimeConfig()` | | Route rules redirect | `statusCode` | `status` | ### File-Based Server Routes ``` server/ ├── api/ # API endpoints (/api/*) │ ├── users/ │ │ ├── index.get.ts → GET /api/users │ │ ├── index.post.ts → POST /api/users │ │ ├── [id].get.ts → GET /api/users/:id │ │ ├── [id].put.ts → PUT /api/users/:id │ │ └── [id].delete.ts → DELETE /api/users/:id │ └── health.get.ts → GET /api/health ├── routes/ ...