Skip to main content

Nuxt.js 4.5.2

Release Date: August 5, 2026

Nuxt.js has released version 4.5.2, a patch update to the Vue-based meta-framework, on August 5, 2026. The release focuses on faster builds, sharper island rendering, and a series of correctness fixes across the Nuxt core, Nitro server engine, and Vite integration.

What Changed

The update is headlined by four performance improvements. Nuxt and its kit layer now skip rewriting generated files that have not changed, use lazy imports to speed up parsing, and reuse app and component scans when project structures are unchanged. On the Vite side, the bare-import resolver no longer probes HTML entries, shaving work off every resolution.

"4.5.2 is the next patch release," the team noted in the release announcement, alongside a changelog of more than twenty fixes.

Why It Matters

Island architecture users get the most attention this cycle. Links inside islands now use client-side navigation, island payloads serialize correctly even when component keys contain underscores, Nitro dedupes island renders during prerendering, and non-object island props are rejected outright. The v-for islands transform also gains Options API support, closing a gap that had forced workarounds.

Build correctness received similar scrutiny: worker builds now share the same asset filenames as the main build, the Vite client manifest path is resolved from the actual config, and build cache collection waits until outputs are final. Developers using preview mode will find it re-checked after prerendered page hydration, and route rules now match against decoded paths.

What Else

The release bundles a refactor to rely on vue-component-type-helpers instead of locally maintained helpers, bumps @nuxt/devtools to v3.4.0, and adds documentation for server components, mostly-static sites, and accessible routing. The testing guide was updated to test-utils v4.1.0. Fourteen contributors are credited, including Daniel Roe and Anthony Fu.

Whats Next

Nuxt 4.5.2 is available now via npx nuxt upgrade. The v3 line, meanwhile, was declared end-of-life in its final 3.21.11 patch, with the team directing remaining v3 users to upgrade to v4. For teams still on v3, this release is the clearest signal yet that the migration window is closing.

What is New?

By continuing to use the site, you agree to the use of cookies.