The lede
Nuxt 4.6
Daniel Roe, Nuxt blog · made the Sunday
Four hundred and twenty commits, and the headline is subtraction: a new `nuxt/server` import surface means your handlers are typed against a portable RequestEvent rather than against whichever h3 and Nitro majors Nuxt happens to depend on, so the same file runs under Nitro v2, Nitro v3 or the new experimental pure-Vite server. Typed `$fetch` has been rebuilt on fetchdts, which is the fix for anyone who has watched TS2589 appear somewhere past their three-hundredth route — resolution now scales with call sites, not route count, and the 1,000-route benchmark goes from 12.8 million instantiations and a 7.4-second typecheck to 51,558 and a fifth of a second, with peak memory falling from 946MB to 140MB. There are also sealed-cookie sessions behind a single derived `appSecret`, so a small app gets auth state with no store to provision. The detail worth sitting with is in the CLI: a lock file in `.nuxt/` lets a second `nuxt dev` — Roe's example is one started by an agent — take over from or defer to the one you started, there are `nuxt curl` and `nuxt task` commands for talking to the running server, and the new error overlay has a copy button that formats the stack trace as a prompt. The framework has started designing for the thing sitting next to you in the terminal.