What changed
Nuxt 4.6 shipped October 5, 2026 with nuxt/server as a public server API that insulates applications from the underlying h3/Nitro version. Nitro remains the default, while @nuxt/vite-server provides an experimental alternative. The release rebuilds typed $fetch on fetchdts to avoid large TypeScript instantiation blowups, adds runtimeConfig.appSecret and sealed-cookie sessions via useSession, supports Vue Vapor interoperability, and ships Nuxt CLI v4 with developer workflow improvements.
Why it matters
Nuxt's server API previously exposed more of Nitro and h3's implementation details, making major dependency transitions disruptive. A stable Nuxt-owned server surface can make framework evolution and hosting choices easier. Meanwhile, the typed-fetch rewrite targets compile-time cost on large route sets, a practical productivity issue for teams with extensive APIs.
nuxt/server becomes the compatibility boundary
Nuxt owns public request/event helpers rather than tying application imports directly to h3/Nitro major versions. Nitro remains the default implementation.
A pure Vite server is still experimental
@nuxt/vite-server previews a different server backend, but production teams should not treat it as an equivalent GA deployment path.
Typed fetch and sessions get practical upgrades
The rebuilt typed $fetch targets excessive TypeScript instantiations on large route sets; appSecret and useSession provide sealed cookie sessions without a mandatory server-side session store.
CLI v4 improves development workflows
The new CLI adds faster startup and clearer errors, plus a lock/takeover mechanism useful when an agent or second terminal starts the dev server.