Documentation
Nuxt 5 Progress
Follow the public Nuxt 5 integration branches and see what is implemented today.
Nuxt Endpoints supports Nuxt 4.5+ today. In parallel, the Nuxt 5 integration is being developed in public against matching H3, Nitro, and fetchdts prototypes. These branches are experimental working branches, not the supported Nuxt 4 release line.
Last updated: 2026-09-04
Working branches
| Project | Branch | Role in the prototype |
|---|---|---|
| Nuxt Endpoints | nuxt5 | Nuxt integration, $endpoint, useEndpoint, OpenAPI, and idempotency UX |
| H3 | prototype/route-contracts | Typed route contracts, validation, and the active contract on the event |
| Nitro | prototype/route-contracts | Build-time contract extraction, metadata, generated types, and runtime wiring |
| fetchdts | prototype/route-contracts | Extensible route metadata carried into generated client types |
The branches are kept together because the current prototype crosses project boundaries. The Nuxt Endpoints branch links these exact forks while the upstream API shape is being worked out.
What stays stable
$endpoint and useEndpoint are useful application-facing APIs independently
of where route-contract discovery and validation live. The Nuxt 5 work therefore
focuses on replacing module-owned lower-level plumbing with upstream primitives,
while preserving that UX and avoiding two permanent implementations of the same
machinery.
Upstream APIs are still evolving, so changes cannot be ruled out. Keeping application code stable wherever practical is nevertheless a design constraint, and unavoidable changes will be documented as migrations.
The mainstream endpoint surface is shared by both lines, including
defineRouteHandler, $endpoint, useEndpoint, idempotency, and the typed
Pinia Colada adapters. Progressive enhancement and explicit authoring for
HEAD, OPTIONS, CONNECT, and TRACE depend on the Nuxt 5 platform line.
For the supported release line, start with Getting Started.