Currency questions are cheap for an interviewer and revealing for a candidate. "What changed in the last release?" separates people who use a framework from people who follow it, and for a tooling role it is close to a job requirement: a layer or module author has to know what is coming before consumers do.
| Thing | Where it is | Notes |
|---|---|---|
| Nuxt 4.5.x | current stable | 4.5.2 is what this app is built on; the 4.5 line brought Vite 8 on Rolldown, Rspack 2 with an Rsbuild pipeline, and experimental SSR streaming |
| Nuxt 4.4.x | previous minor | the 4.4 line carried security releases; 4.5.1 followed on the 4.5 line |
| Nuxt 3 | end of life | since 31 July 2026; consumers still on 3.x need migrating, not patching |
| Nuxt 5 | in development | opt in on a 4.x project with future.compatibilityVersion: 5; Nitro v3, Vite Environment API, and a list of behaviour changes documented in the upgrade guide |
| Vue 3.5.x | current stable | useId, useTemplateRef, lazy hydration strategies, data-allow-mismatch |
| Vue 3.6 | release candidates | Vapor mode; check its status the week of the interview rather than claiming it |
| Nitro | 2.x under Nuxt 4 | Nitro v3 is what Nuxt 5 targets; nitro.build documents v3, so prefer nuxt.com for Nuxt 4 behaviour |
enforce assumptions and our optimizeDeps entries" is an answer."4.5 is current, and it was mostly plumbing: Vite 8 on Rolldown, Rspack 2 as an alternative builder, experimental SSR streaming, plus security releases on the 4.4 and 4.5 lines. Nuxt 3 went end of life at the end of July 2026, so anything still on 3 is a migration rather than an upgrade. Nuxt 5 is in development and you can opt into its behaviour today with future.compatibilityVersion: 5 — the headline changes are Nitro v3, Vite's Environment API and a set of smaller behavioural fixes. For our tooling that means a CI matrix against the lowest version we support, latest, and nightly, so I find out about breakage before consumers do."
pnpm validate-style check on yourself: for every claim in this section, find the page that proves it. The ones you cannot prove are the ones to re-verify.Rollout and breaking changes
What counts as breaking for a layer and for a module, the deprecate-warn-codemod-remove sequence, and how to roll a change out to twenty apps without an incident.
What Nuxt 4.5 changed
Vite 8 on Rolldown, the Rspack builder, experimental SSR streaming and the security releases, read from a layer and module author's point of view.