Nuxt

v4.4.6 shipped in May, closing a batch of SSR module cache, resolveComponent, and payload cache bugs across both the v4 and v3 branches.¹

Stop repeating options in every composable call. v4.4.0 shipped createUseFetch and createUseAsyncData factories so teams set project-wide defaults once — base URLs, server: false, and other recurring options no longer scatter across every call site.² Vue Router v5 is now the default, with tighter navigation-guard types.³ A new accessibility announcer handles route-transition announcements automatically. Typed layout props, build profiling printed directly in CLI output, and smarter payload handling for data-heavy pages round out the minor.

Patch cycles tightened both active branches. Recent v4.4.3–v4.4.6 and v3.21.3–v3.21.6 patches addressed:

• Recursive rendering deadlocks during prerender (nitro)⁴
• SSR module cache invalidation on plugin-hook changes (vite)⁵
• useFetch key not updating when watch: false
• Redundant CSS link dropped when entry styles are inlined
• useLoadingIndicator properties marked readonly
• setPageLayout props now preserved on same-path navigation

Ask your framework questions on the docs site and get a real answer. The Nuxt Agent — launched in late April 2026 — is an AI assistant on nuxt.com grounded in official docs and the ecosystem.⁶ Built with the Vercel AI SDK, their own MCP server, and Nuxt UI components, it replaced the previous Kapa.ai widget with a deeper integration.⁷ Open it anywhere on nuxt.com with ⌘I or visit /chat for the full-screen experience.