@nuxt/docs 4.2.2 → 4.3.1

package/4.api/3.utils/define-page-meta.md

@@ -32,6 +32,7 @@ interface PageMeta {
   path?: string
   props?: RouteRecordRaw['props']
   alias?: string | string[]
+  groups?: string[]
   pageTransition?: boolean | TransitionProps
   layoutTransition?: boolean | TransitionProps
   viewTransition?: boolean | 'always'
@@ -76,6 +77,12 @@ interface PageMeta {
 
     Aliases for the record. Allows defining extra paths that will behave like a copy of the record. Allows having paths shorthands like `/users/:id` and `/u/:id`. All `alias` and `path` values must share the same params.
 
+  **`groups`**
+
+  - **Type**: `string[]`
+
+    Route groups the page belongs to, based on the folder structure. Automatically populated for pages within [route groups](/docs/4.x/guide/directory-structure/app/pages#route-groups).
+
   **`keepalive`**
 
   - **Type**: `boolean` | [`KeepAliveProps`](https://vuejs.org/api/built-in-components#keepalive)
@@ -130,7 +137,7 @@ interface PageMeta {
 
   - **Type**: `(route: RouteLocationNormalized) => boolean | Promise<boolean> | Partial<NuxtError> | Promise<Partial<NuxtError>>`
 
-    Validate whether a given route can validly be rendered with this page. Return true if it is valid, or false if not. If another match can't be found, this will mean a 404. You can also directly return an object with `statusCode`/`statusMessage` to respond immediately with an error (other matches will not be checked).
+    Validate whether a given route can validly be rendered with this page. Return true if it is valid, or false if not. If another match can't be found, this will mean a 404. You can also directly return an object with `status`/`statusText` to respond immediately with an error (other matches will not be checked).
 
   **`scrollToTop`**
 

package/4.api/3.utils/set-page-layout.md

@@ -19,6 +19,42 @@ export default defineNuxtRouteMiddleware((to) => {
 })
 ```
 
+## Passing Props to Layouts
+
+You can pass props to the layout by providing an object as the second argument:
+
+```ts [app/middleware/admin-layout.ts]
+export default defineNuxtRouteMiddleware((to) => {
+  setPageLayout('admin', {
+    sidebar: true,
+    title: 'Dashboard',
+  })
+})
+```
+
+The layout can then receive these props:
+
+```vue [app/layouts/admin.vue]
+<script setup lang="ts">
+const props = defineProps<{
+  sidebar?: boolean
+  title?: string
+}>()
+</script>
+
+<template>
+  <div>
+    <aside v-if="sidebar">
+      Sidebar
+    </aside>
+    <main>
+      <h1>{{ title }}</h1>
+      <slot />
+    </main>
+  </div>
+</template>
+```
+
 ::note
 If you choose to set the layout dynamically on the server side, you _must_ do so before the layout is rendered by Vue (that is, within a plugin or route middleware) to avoid a hydration mismatch.
 ::

package/4.api/3.utils/set-response-status.md

@@ -1,6 +1,6 @@
 ---
 title: 'setResponseStatus'
-description: setResponseStatus sets the statusCode (and optionally the statusMessage) of the response.
+description: setResponseStatus sets the status (and optionally the statusText) of the response.
 links:
   - label: Source
     icon: i-simple-icons-github
@@ -10,7 +10,7 @@ links:
 
 Nuxt provides composables and utilities for first-class server-side-rendering support.
 
-`setResponseStatus` sets the statusCode (and optionally the statusMessage) of the response.
+`setResponseStatus` sets the status (and optionally the statusText) of the response.
 
 ::important
 `setResponseStatus` can only be called in the [Nuxt context](/docs/4.x/guide/going-further/nuxt-app#the-nuxt-context).

package/4.api/3.utils/show-error.md

@@ -12,13 +12,13 @@ Within the [Nuxt context](/docs/4.x/guide/going-further/nuxt-app#the-nuxt-contex
 
 **Parameters:**
 
-- `error`: `string | Error | Partial<{ cause, data, message, name, stack, statusCode, statusMessage }>`
+- `error`: `string | Error | Partial<{ cause, data, message, name, stack, status, statusText }>`
 
 ```ts
 showError('😱 Oh no, an error has been thrown.')
 showError({
-  statusCode: 404,
-  statusMessage: 'Page Not Found',
+  status: 404,
+  statusText: 'Page Not Found',
 })
 ```
 

package/4.api/4.commands/add.md

@@ -4,7 +4,7 @@ description: "Scaffold an entity into your Nuxt application."
 links:
   - label: Source
     icon: i-simple-icons-github
-    to: https://github.com/nuxt/cli/blob/main/packages/nuxi/src/commands/add.ts
+    to: https://github.com/nuxt/cli/blob/main/packages/nuxi/src/commands/add-template.ts
     size: xs
 ---
 
@@ -23,7 +23,7 @@ npx nuxt add <TEMPLATE> <NAME> [--cwd=<directory>] [--logLevel=<silent|info|verb
 | `NAME`     | Specify name of the generated file                                                                                                                                                                               |
 <!--/add-args-->
 
-### Options
+## Options
 
 <!--add-opts-->
 | Option                               | Default | Description                              |

package/4.api/5.kit/1.modules.md

@@ -64,7 +64,7 @@ export function defineNuxtModule<TOptions extends ModuleOptions> (): {
 | `hooks`              | `Partial<NuxtHooks>`{lang="ts"}                                                                                   | `false`  | Hooks to be installed for the module. If provided, the module will install the hooks.                                                                                                                              |
 | `moduleDependencies` | `Record<string, ModuleDependency> \| ((nuxt: Nuxt) => Record<string, ModuleDependency>)`{lang="ts"}               | `false`  | Dependencies on other modules with version constraints and configuration. Can be an object or a function that receives the Nuxt instance. See [example](/docs/4.x/api/kit/modules#specifying-module-dependencies). |
 | `onInstall`          | `(nuxt: Nuxt) => Awaitable<void>`{lang="ts"}                                                                      | `false`  | Lifecycle hook called when the module is first installed. Requires `meta.name` and `meta.version` to be defined.                                                                                                   |
-| `onUpgrade`          | `(options: T, nuxt: Nuxt, previousVersion: string) => Awaitable<void>`{lang="ts"}                                 | `false`  | Lifecycle hook called when the module is upgraded to a newer version. Requires `meta.name` and `meta.version` to be defined.                                                                                       |
+| `onUpgrade`          | `(nuxt: Nuxt, options: T, previousVersion: string) => Awaitable<void>`{lang="ts"}                                 | `false`  | Lifecycle hook called when the module is upgraded to a newer version. Requires `meta.name` and `meta.version` to be defined.                                                                                       |
 | `setup`              | `(this: void, resolvedOptions: T, nuxt: Nuxt) => Awaitable<void \| false \| ModuleSetupInstallResult>`{lang="ts"} | `false`  | Setup function for the module. If provided, the module will call the setup function.                                                                                                                               |
 
 ### Examples
@@ -103,6 +103,19 @@ export default defineNuxtConfig({
 })
 ```
 
+Users can also completely disable a module by setting the config key to `false`. This prevents the module's setup function from running while still generating types for module options.
+
+```ts
+export default defineNuxtConfig({
+  // Disable the module entirely
+  myModule: false,
+})
+```
+
+::tip
+This is particularly useful when you want to disable modules inherited from [Nuxt layers](/docs/4.x/guide/going-further/layers#disabling-modules-from-layers).
+::
+
 #### Defining Module Compatibility Requirements
 
 If you're developing a Nuxt module and using APIs that are only supported in specific Nuxt versions, it's highly recommended to include `compatibility.nuxt`.
@@ -216,7 +229,7 @@ export default defineNuxtModule({
     // - Perform initial data migration
   },
 
-  onUpgrade (options, nuxt, previousVersion) {
+  onUpgrade (nuxt, options, previousVersion) {
     // This runs when the module is upgraded to a newer version
     console.log(`Upgrading my-awesome-module from ${previousVersion} to 1.2.0`)
 

package/4.api/5.kit/11.nitro.md

@@ -301,6 +301,10 @@ function addPrerenderRoutes (routes: string | string[]): void
 
 Add imports to the server. It makes your imports available in Nitro without the need to import them manually.
 
+::warning
+If you want to provide a utility that works in both server and client contexts and is usable in the [`shared/`](/docs/4.x/directory-structure/shared) directory, the function must be imported from the same source file for both [`addImports`](/docs/4.x/api/kit/autoimports#addimports) and `addServerImports` and should have identical signature. That source file should not import anything context-specific (i.e., Nitro context, Nuxt app context) or else it might cause errors during type-checking.
+::
+
 ### Usage
 
 ```ts twoslash
@@ -422,10 +426,10 @@ export default defineEventHandler(() => {
 ## `addServerScanDir`
 
 Add directories to be scanned by Nitro. It will check for subdirectories, which will be registered
-just like the `~/server` folder is.
+just like the `~~/server` folder is.
 
 ::note
-Only `~/server/api`, `~/server/routes`, `~/server/middleware`, and `~/server/utils` are scanned.
+Only `~~/server/api`, `~~/server/routes`, `~~/server/middleware`, and `~~/server/utils` are scanned.
 ::
 
 ### Usage

package/4.api/5.kit/14.builder.md

@@ -207,7 +207,19 @@ See [Vite website](https://vite.dev/guide/api-plugin) for more information about
 
 ### Parameters
 
-**`pluginOrGetter`**: A Vite plugin instance or an array of Vite plugin instances. If a function is provided, it must return a Vite plugin instance or an array of Vite plugin instances.
+**`pluginOrGetter`**: A Vite plugin instance or an array of Vite plugin instances. If a function is provided, it must return a Vite plugin instance or an array of Vite plugin instances. The function can also be async or return a Promise, which is useful for lazy-loading plugins:
+
+```ts twoslash
+// @errors: 2307
+import { addVitePlugin, defineNuxtModule } from '@nuxt/kit'
+
+export default defineNuxtModule({
+  setup () {
+    // Lazy load the plugin - only imported when the build actually runs
+    addVitePlugin(() => import('my-vite-plugin').then(r => r.default()))
+  },
+})
+```
 
 **`options`**: Options to pass to the callback function. This object can have the following properties:
 
@@ -266,7 +278,7 @@ See [webpack website](https://webpack.js.org/concepts/plugins/) for more informa
 
 ### Parameters
 
-**`pluginOrGetter`**: A webpack plugin instance or an array of webpack plugin instances. If a function is provided, it must return a webpack plugin instance or an array of webpack plugin instances.
+**`pluginOrGetter`**: A webpack plugin instance or an array of webpack plugin instances. If a function is provided, it must return a webpack plugin instance or an array of webpack plugin instances. The function can also be async or return a Promise, enabling lazy-loading of plugins.
 
 **`options`**: Options to pass to the callback function. This object can have the following properties:
 

package/4.api/5.kit/4.autoimports.md

@@ -24,7 +24,11 @@ Watch Vue School video about Auto-imports Nuxt Kit utilities.
 
 ## `addImports`
 
-Add imports to the Nuxt application. It makes your imports available in the Nuxt application without the need to import them manually.
+Add imports to the Nuxt application. It makes your imports available in the Nuxt app context without the need to import them manually.
+
+::tip
+To add imports for the Nitro server context, refer to the [`addServerImports`](/docs/4.x/api/kit/nitro#addserverimports) function.
+::
 
 ### Usage
 

package/4.api/6.nuxt-config.md

@@ -13,12 +13,13 @@ You can improve your DX by defining additional aliases to access custom director
 - **Default**
 ```json
 {
-  "~": "/<srcDir>",
-  "@": "/<srcDir>",
+  "~": "/<rootDir>/app",
+  "@": "/<rootDir>/app",
   "~~": "/<rootDir>",
   "@@": "/<rootDir>",
   "#shared": "/<rootDir>/shared",
-  "assets": "/<srcDir>/assets",
+  "#server": "/<rootDir>/server",
+  "assets": "/<rootDir>/app/assets",
   "public": "/<rootDir>/public",
   "#build": "/<rootDir>/.nuxt",
   "#internal/nuxt/paths": "/<rootDir>/.nuxt/paths.mjs"
@@ -210,7 +211,7 @@ Default values for layout transitions.
 
 This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
 
-- **Type**: `boolean`
+- **Type**: `boolean | TransitionProps`
 - **Default:** `false`
 
 **See**: [Vue Transition docs](https://vuejs.org/api/built-in-components#transition)
@@ -221,7 +222,7 @@ Default values for page transitions.
 
 This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
 
-- **Type**: `boolean`
+- **Type**: `boolean | TransitionProps`
 - **Default:** `false`
 
 **See**: [Vue Transition docs](https://vuejs.org/api/built-in-components#transition)
@@ -372,7 +373,7 @@ export default defineNuxtConfig({
   build: {
     templates: [
       {
-        src: '~/modules/support/plugin.js', // `src` can be absolute or relative
+        src: '~~/modules/support/plugin.js', // `src` can be absolute or relative
         dst: 'support.js', // `dst` is relative to project `.nuxt` dir
       },
     ],
@@ -880,7 +881,7 @@ Defaults to 'silent' when running in CI or when a TTY is not available. This opt
 Modules are Nuxt extensions which can extend its core functionality and add endless integrations.
 
 Each module is either a string (which can refer to a package, or be a path to a file), a tuple with the module as first string and the options as a second object, or an inline module function.
-Nuxt tries to resolve each item in the modules array using node require path (in `node_modules`) and then will be resolved from project `srcDir` if `~` alias is used.
+Nuxt tries to resolve each item in the modules array using node require path (in `node_modules`) and then will be resolved from project `rootDir` if `~~` alias is used.
 
 - **Type**: `array`
 
@@ -895,8 +896,8 @@ export default defineNuxtConfig({
   modules: [
   // Using package name
     '@nuxt/scripts',
-    // Relative to your project srcDir
-    '~/custom-modules/awesome.js',
+    // Relative to your project rootDir
+    '~~/custom-modules/awesome.js',
     // Providing options
     ['@nuxtjs/google-analytics', { ua: 'X1234567' }],
     // Inline definition
@@ -1013,8 +1014,12 @@ Options passed directly to the transformer from `unctx` that preserves async con
 
 Functions to inject a key for.
 
-As long as the number of arguments passed to the function is less than `argumentLength`, an additional magic string will be injected that can be used to deduplicate requests between server and client. You will need to take steps to handle this additional key.
-The key will be unique based on the location of the function being invoked within the file.
+As long as the number of arguments passed to the function is less than `argumentLength`, an additional magic string will be injected as the last argument. This key is stable between SSR and client-side hydration. You will need to take steps to handle this additional key.
+The key is unique based on the location of the function being invoked within the file.
+
+::read-more{to="/docs/4.x/guide/modules/recipes-basics#add-keyed-functions"}
+Learn more about keyed functions.
+::
 
 - **Type**: `array`
 - **Default**
@@ -1022,31 +1027,38 @@ The key will be unique based on the location of the function being invoked withi
 [
   {
     "name": "callOnce",
-    "argumentLength": 3
+    "argumentLength": 3,
+    "source": "#app/composables/once"
   },
   {
     "name": "defineNuxtComponent",
-    "argumentLength": 2
+    "argumentLength": 2,
+    "source": "#app/composables/component"
   },
   {
     "name": "useState",
-    "argumentLength": 2
+    "argumentLength": 2,
+    "source": "#app/composables/state"
   },
   {
     "name": "useFetch",
-    "argumentLength": 3
+    "argumentLength": 3,
+    "source": "#app/composables/fetch"
   },
   {
     "name": "useAsyncData",
-    "argumentLength": 3
+    "argumentLength": 3,
+    "source": "#app/composables/asyncData"
   },
   {
     "name": "useLazyAsyncData",
-    "argumentLength": 3
+    "argumentLength": 3,
+    "source": "#app/composables/asyncData"
   },
   {
     "name": "useLazyFetch",
-    "argumentLength": 3
+    "argumentLength": 3,
+    "source": "#app/composables/fetch"
   }
 ]
 ```
@@ -1297,7 +1309,7 @@ Define the server directory of your Nuxt application, where Nitro routes, middle
 If a relative path is specified, it will be relative to your `rootDir`.
 
 - **Type**: `string`
-- **Default:** `"/<srcDir>/server"`
+- **Default:** `"/<rootDir>/server"`
 
 ## serverHandlers
 
@@ -1318,7 +1330,7 @@ Each handler accepts the following options:
 ```ts
 export default defineNuxtConfig({
   serverHandlers: [
-    { route: '/path/foo/**:name', handler: '~/server/foohandler.ts' },
+    { route: '/path/foo/**:name', handler: '#server/foohandler.ts' },
   ],
 })
 ```
@@ -1408,22 +1420,27 @@ export default defineNuxtConfig({
   srcDir: 'app/',
 })
 ```
+
 This expects the following folder structure:
 ```bash
 -| app/
 ---| assets/
 ---| components/
+---| composables/
 ---| layouts/
 ---| middleware/
 ---| pages/
 ---| plugins/
+---| utils/
 ---| app.config.ts
 ---| app.vue
 ---| error.vue
 -| server/
+-| shared/
 -| public/
 -| modules/
--| nuxt.config.js
+-| layers/
+-| nuxt.config.ts
 -| package.json
 ```
 
@@ -1692,7 +1709,7 @@ Please note that not all vite options are supported in Nuxt.
 ### `root`
 
 - **Type**: `string`
-- **Default:** `"/<srcDir>"`
+- **Default:** `"/<rootDir>"`
 
 ### `server`
 
@@ -1705,7 +1722,7 @@ Please note that not all vite options are supported in Nuxt.
 ```json
 [
   "/<rootDir>/.nuxt",
-  "/<srcDir>",
+  "/<rootDir>/app",
   "/<rootDir>",
   "/<workspaceDir>"
 ]

package/5.community/4.contribution.md

@@ -11,7 +11,7 @@ There is a range of different ways you might be able to contribute to the Nuxt e
 The Nuxt ecosystem includes many different projects and organizations:
 
 * [nuxt/](https://github.com/nuxt) - core repositories for the Nuxt framework itself. [**nuxt/nuxt**](https://github.com/nuxt/nuxt) contains the Nuxt framework (both versions 2 and 3).
-* [nuxt-modules/](https://github.com/nuxt-modules) - community-contributed and maintained modules and libraries. There is a [process to migrate a module](/docs/4.x/guide/going-further/modules/#joining-nuxt-modules-and-nuxtjs) to `nuxt-modules`. While these modules have individual maintainers, they are not dependent on a single person.
+* [nuxt-modules/](https://github.com/nuxt-modules) - community-contributed and maintained modules and libraries. There is a [process to migrate a module](/docs/4.x/guide/modules/ecosystem) to `nuxt-modules`. While these modules have individual maintainers, they are not dependent on a single person.
 * [unjs/](https://github.com/unjs) - many of these libraries are used throughout the Nuxt ecosystem. They are designed to be universal libraries that are framework- and environment-agnostic. We welcome contributions and usage by other frameworks and projects.
 
 ## How To Contribute
@@ -100,7 +100,7 @@ Our aim is ensuring quality and maintaining the joy of collaborating and communi
 
 ### Create a Module
 
-If you've built something with Nuxt that's cool, why not [extract it into a module](/docs/4.x/guide/going-further/modules), so it can be shared with others? We have [many excellent modules already](/modules), but there's always room for more.
+If you've built something with Nuxt that's cool, why not [extract it into a module](/docs/4.x/guide/modules), so it can be shared with others? We have [many excellent modules already](/modules), but there's always room for more.
 
 If you need help while building it, feel free to [check in with us](/docs/4.x/community/getting-help).
 
@@ -126,7 +126,7 @@ The following conventions are _required_ within the `nuxt/` organization and rec
 
 #### Module Conventions
 
-Modules should follow the [Nuxt module template](https://github.com/nuxt/starter/tree/module). See [module guide](/docs/4.x/guide/going-further/modules) for more information.
+Modules should follow the [Nuxt module template](https://github.com/nuxt/starter/tree/module). See [module guide](/docs/4.x/guide/modules) for more information.
 
 #### Use Core `unjs/` Libraries
 
@@ -134,7 +134,7 @@ We recommend the following libraries which are used throughout the ecosystem:
 
 * [pathe](https://github.com/unjs/pathe) - universal path utilities (replacement for node `path`)
 * [ufo](https://github.com/unjs/ufo) - URL parsing and joining utilities
-* [unbuild](https://github.com/unjs/unbuild) - rollup-powered build system
+* [obuild](https://github.com/unjs/obuild) - rolldown-powered build system
 * ... check out the rest of the [unjs/](https://github.com/unjs) organization for many more!
 
 #### Use ESM Syntax and Default to `type: module`
@@ -172,7 +172,7 @@ We recommend using [VS Code](https://code.visualstudio.com) along with the [ESLi
 
 #### No Prettier
 
-Since ESLint is already configured to format the code, there is no need to duplicate the functionality with Prettier. To format the code, you can run `yarn lint --fix`, `pnpm lint --fix`, or `bun run lint --fix` or referring the [ESLint section](/docs/4.x/community/contribution#use-eslint) for IDE Setup.
+Since ESLint is already configured to format the code, there is no need to duplicate the functionality with Prettier. To format the code, you can run `yarn lint --fix`, `pnpm lint --fix`, `bun run lint --fix`, or `deno run lint --fix` or referring the [ESLint section](/docs/4.x/community/contribution#use-eslint) for IDE Setup.
 
 If you have Prettier installed in your editor, we recommend you disable it when working on the project to avoid conflict.
 

package/5.community/5.framework-contribution.md

@@ -8,7 +8,7 @@ Once you've read the [general contribution guide](/docs/4.x/community/contributi
 
 ## Monorepo Guide
 
-- `packages/kit`: Toolkit for authoring Nuxt Modules, published as [`@nuxt/kit`](https://www.npmjs.com/package/@nuxt/kit).
+- `packages/kit`: Toolkit for authoring Nuxt modules, published as [`@nuxt/kit`](https://www.npmjs.com/package/@nuxt/kit).
 - `packages/nuxt`: The core of Nuxt, published as [`nuxt`](https://www.npmjs.com/package/nuxt).
 - `packages/schema`: Cross-version Nuxt typedefs and defaults, published as [`@nuxt/schema`](https://www.npmjs.com/package/@nuxt/schema).
 - `packages/rspack`: The [Rspack](https://rspack.rs) bundler for Nuxt, published as [`@nuxt/rspack-builder`](https://www.npmjs.com/package/@nuxt/rspack-builder).

package/5.community/6.roadmap.md

@@ -42,7 +42,7 @@ In addition to the Nuxt framework, there are modules that are vital for the ecos
 |----------------------------------------|--------------|--------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [Scripts](https://scripts.nuxt.com)    | Public Beta  | 3.x, 4.x     | [nuxt/scripts](https://github.com/nuxt/scripts) | Easy 3rd party script management.                                                                                                                                    |
 | Auth Utils                             | Planned      | 4.x, 5.x     | `nuxt/auth-utils` to be announced               | The temporary repository [atinux/nuxt-auth-utils](https://github.com/atinux/nuxt-auth-utils) is available while awaiting its official integration into Nuxt via RFC. |
-| A11y                                   | Planned      | 4.x, 5.x     | `nuxt/a11y` to be announced                     | Accessibility hinting and utilities [nuxt/nuxt#23255](https://github.com/nuxt/nuxt/issues/23255)                                                                     |
+| [a11y](https://github.com/nuxt/a11y)   | Public Alpha | 3.x, 4.x     | [nuxt/a11y](https://github.com/nuxt/a11y).      | Real-time accessibility feedback and automated testing in your browser during development (see [nuxt/nuxt#23255](https://github.com/nuxt/nuxt/issues/23255)).        |
 | [Hints](https://github.com/nuxt/hints) | Public Alpha | 4.x, 5.x     | [nuxt/hints](https://github.com/nuxt/hints)     | Guidance and suggestions for enhancing development practices.                                                                                                        |
 
 ## Release Cycle
@@ -61,15 +61,15 @@ We commit to support each major version of Nuxt for a minimum of six months afte
 
 The current active version of [Nuxt](https://nuxt.com) is **v4** which is available as `nuxt` on npm with the `latest` tag.
 
-Nuxt 3 will continue to receive maintenance updates (both bug fixes and backports of features from Nuxt 4) until the end of January 2026.
+Nuxt 3 will continue to receive maintenance updates (bug fixes and security patches) until the end of July 2026.
 
 Each active version has its own nightly releases which are generated automatically. For more about enabling the Nuxt nightly release channel, see [the nightly release channel docs](/docs/4.x/guide/going-further/nightly-release-channel).
 
 | Release               |                                                                                                                                                                                                                                                    | Initial release     | End Of Life                | Docs                                                              |
 |-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------|-------------------------------------------------------------------|
-| **5.x** (scheduled)   |                                                                                                                                                                                                                                                    | Q4 2025 (estimated) | TBA                        |                                                              |
+| **5.x** (scheduled)   |                                                                                                                                                                                                                                                    | Q1 2026 (estimated) | TBA                        |                                                              |
 | **4.x** (stable)      | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt latest version" src="https://img.shields.io/npm/v/nuxt.svg?logo=nuxt&label=&style=flat&colorA=18181B&colorB=28CF8D" class="not-prose h-5 w-auto" :zoom="false"></a> | 2025-07-16          | 6 months after 5.x release | [nuxt.com](/docs/4.x/getting-started/introduction)                |
-| **3.x** (maintenance) | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 3.x version" src="https://img.shields.io/npm/v/nuxt/3x.svg?logo=nuxt&label=&style=flat&colorA=18181B&colorB=28CF8D" class="not-prose h-5 w-auto" :zoom="false"></a> | 2022-11-16          | 2026-01-31                 | [nuxt.com](/docs/3.x/getting-started/introduction)                |
+| **3.x** (maintenance) | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 3.x version" src="https://img.shields.io/npm/v/nuxt/3x.svg?logo=nuxt&label=&style=flat&colorA=18181B&colorB=28CF8D" class="not-prose h-5 w-auto" :zoom="false"></a> | 2022-11-16          | 2026-07-31                 | [nuxt.com](/docs/3.x/getting-started/introduction)                |
 | **2.x** (unsupported) | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 2.x version" src="https://img.shields.io/npm/v/nuxt/2x.svg?logo=nuxt&label=&style=flat&colorA=18181B&colorB=28CF8D" class="not-prose h-5 w-auto" :zoom="false"></a> | 2018-09-21          | 2024-06-30                 | [v2.nuxt.com](https://v2.nuxt.com/docs/get-started/installation/) |
 | **1.x** (unsupported) | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 1.x version" src="https://img.shields.io/npm/v/nuxt/1x.svg?logo=nuxt&label=&style=flat&colorA=18181B&colorB=28CF8D" class="not-prose h-5 w-auto" :zoom="false"></a> | 2018-01-08          | 2019-09-21                 | &nbsp;                                                            |
 

package/5.community/7.changelog.md

@@ -28,6 +28,16 @@ navigation.icon: i-lucide-bell-dot
   ::card
   ---
   icon: i-simple-icons-github
+  title: nuxt/a11y
+  to: https://github.com/nuxt/a11y/releases
+  target: _blank
+  ui.icon.base: text-black dark:text-white
+  ---
+  Nuxt A11y releases.
+  ::
+  ::card
+  ---
+  icon: i-simple-icons-github
   title: nuxt/content
   to: https://github.com/nuxt/content/releases
   target: _blank

package/6.bridge/1.overview.md

@@ -46,6 +46,10 @@ pnpm install
 bun install
 ```
 
+```bash [deno]
+deno install
+```
+
 ::
 
 ::note
@@ -74,6 +78,10 @@ pnpm add -D @nuxt/bridge nuxi
 bun add -D @nuxt/bridge nuxi
 ```
 
+```bash [deno]
+deno add -D npm:@nuxt/bridge npm:nuxi
+```
+
 ::
 
 ### Update `nuxt.config`

package/6.bridge/4.plugins-and-middleware.md

@@ -46,7 +46,7 @@ Use of `defineNuxtRouteMiddleware` is not supported outside of the `app/middlewa
 
 You can also use [`definePageMeta`](/docs/4.x/api/utils/define-page-meta) in Nuxt Bridge.
 
-You can be enabled with the `macros.pageMeta` option in your configuration file
+It can be enabled with the `macros.pageMeta` option in your configuration file
 
 ```ts [nuxt.config.ts]
 import { defineNuxtConfig } from '@nuxt/bridge'

package/6.bridge/8.nitro.md

@@ -45,6 +45,10 @@ pnpm add -D nuxi
 bun add -D nuxi
 ```
 
+```bash [deno]
+deno add -D npm:nuxi
+```
+
 ::
 
 ### Nuxi

package/7.migration/11.server.md

@@ -10,7 +10,7 @@ In a built Nuxt 3 application, there is no runtime Nuxt dependency. That means y
 ## Steps
 
 1. Remove the `render` key in your `nuxt.config`.
-2. Any files in `~/server/api` and `~/server/middleware` will be automatically registered; you can remove them from your `serverMiddleware` array.
+2. Any files in `~~/server/api` and `~~/server/middleware` will be automatically registered; you can remove them from your `serverMiddleware` array.
 3. Update any other items in your `serverMiddleware` array to point to files or npm packages directly, rather than using inline functions.
 
 :read-more{to="/docs/4.x/directory-structure/server"}

package/7.migration/2.configuration.md

@@ -115,7 +115,7 @@ Nuxt has built-in support for loading `.env` files. Avoid directly importing it
 
 ## Modules
 
-Nuxt and Nuxt Modules are now build-time-only.
+Nuxt and Nuxt modules are now build-time-only.
 
 ### Migration
 
@@ -133,7 +133,7 @@ Nuxt and Nuxt Modules are now build-time-only.
 ```
 
 ::tip
-If you are a module author, you can check out [more information about module compatibility](/docs/4.x/migration/module-authors) and [our module author guide](/docs/4.x/guide/going-further/modules).
+If you are a module author, you can check out [more information about module compatibility](/docs/4.x/migration/module-authors) and [our module author guide](/docs/4.x/guide/modules).
 ::
 
 ## Directory Changes

package/7.migration/20.module-authors.md

@@ -7,7 +7,7 @@ description: 'Learn how to migrate from Nuxt 2 to Nuxt 3 modules.'
 
 Nuxt 3 has a basic backward compatibility layer for Nuxt 2 modules using `@nuxt/kit` auto wrappers. But there are usually steps to follow to make modules compatible with Nuxt 3 and sometimes, using Nuxt Bridge is required for cross-version compatibility.
 
-We have prepared a [Dedicated Guide](/docs/4.x/guide/going-further/modules) for authoring Nuxt 3 ready modules using `@nuxt/kit`. Currently best migration path is to follow it and rewrite your modules. Rest of this guide includes preparation steps if you prefer to avoid a full rewrite yet making modules compatible with Nuxt 3.
+We have prepared a [Dedicated Guide](/docs/4.x/guide/modules) for authoring Nuxt 3 ready modules using `@nuxt/kit`. Currently best migration path is to follow it and rewrite your modules. Rest of this guide includes preparation steps if you prefer to avoid a full rewrite yet making modules compatible with Nuxt 3.
 
 ::tip{icon="i-lucide-puzzle" to="/modules"}
 Explore Nuxt 3 compatible modules.
@@ -78,7 +78,7 @@ Your module should work even if it's only added to [`buildModules`](/docs/4.x/ap
 (*) Unless it is for `nuxt dev` purpose only and guarded with `if (nuxt.options.dev) { }`.
 
 ::tip
-Continue reading about Nuxt 3 modules in the [Modules Author Guide](/docs/4.x/guide/going-further/modules).
+Continue reading about Nuxt 3 modules in the [Modules Author Guide](/docs/4.x/guide/modules).
 ::
 
 ### Use TypeScript (Optional)

package/7.migration/7.component-options.md

@@ -124,7 +124,7 @@ Similar to `key`, specify it within the [`definePageMeta`](/docs/4.x/api/utils/d
 
 ## `validate`
 
-The validate hook in Nuxt 3 only accepts a single argument, the `route`. Just as in Nuxt 2, you can return a boolean value. If you return false and another match can't be found, this will mean a 404. You can also directly return an object with `statusCode`/`statusMessage` to respond immediately with an error (other matches will not be checked).
+The validate hook in Nuxt 3 only accepts a single argument, the `route`. Just as in Nuxt 2, you can return a boolean value. If you return false and another match can't be found, this will mean a 404. You can also directly return an object with `status`/`statusText` to respond immediately with an error (other matches will not be checked).
 
 ```diff [app/pages/users/[id\\].vue]
 - <script>