Nuxt

A MacOS dev server fix landed in v4.4.8 and v3.21.8, resolving a socket-name length issue that prevented the dev server from starting on that platform.¹

Security patches closed several traversal and protocol risks. v4.4.7 and v3.21.7 addressed:

• Sibling-directory traversal in the test component wrapper²
• Build cache path boundary check using pathe resolve
• Protocol validation in reloadNuxtApp before reload³

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.

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, SSR module cache invalidation on plugin-hook changes, useFetch key not updating when watch: false, and redundant CSS links dropped when entry styles are inlined.

Nuxi brought a named identity to the on-site AI assistant.⁴ The docs chat experience — launched in beta as the Nuxt Agent in April 2026 — was rebranded as Nuxi in May with a deeper integration into nuxt.com. Built with the Vercel AI SDK, the team's own MCP server, and Nuxt UI components, Nuxi is grounded in official docs, modules, and deployment guides. Open it anywhere with ⌘I or visit /chat for the full-screen experience.⁵