what stackpulse tracks
Nuxt releases from GitHub
StackPulse watches Nuxt release notes and keeps the original source link close to every summary.
The intuitive Vue framework StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Nuxt release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
Nuxt 4.6.4 is a security release fixing eight Nuxt advisories and incorporating Nitro 2.13.6, which fixes three additional advisories. It also changes production error-detail exposure, development-server Host validation, workspace detection, route-rule matching, and Nitro caching and proxy behavior.
Nuxt users, particularly those running development servers on custom hosts or relying on the changed error, workspace, route-rule, or Nitro caching and proxy behavior, are affected.
Upgrade to Nuxt 4.6.4 as soon as possible to receive the security fixes; configure `devServer.allowedHosts` if you use a custom hostname or tunnel.
Nuxt 4.6.0 introduces a major update to the CLI with performance improvements and new features, and moves towards server-agnosticism with the new `nuxt/server` API. It also includes breaking changes requiring newer Node.js versions and dropping support for Nuxt 2/3/bridge.
Nuxt users, especially those on older Node.js versions or using Nuxt 2/3/bridge, are affected by the breaking changes.
Upgrade to Nuxt 4.6.0 and review breaking changes if using older Node.js versions or Nuxt 2/3/bridge.
Nuxt 4.5.0 introduces major upgrades including Vite 8, Rspack 2, and experimental SSR streaming, while laying groundwork for Nuxt 5. It also marks the approach of Nuxt 3's end-of-life.
Users on Nuxt 3 should plan migration to v4; those with custom Vite or Rspack configurations may need adjustments.
Review the upgrade guide and test Vite 8 compatibility before upgrading production environments.