@nuxt/docs 3.20.2 → 3.21.1

package/5.community/6.roadmap.md

@@ -28,22 +28,22 @@ In roadmap below are some features we are planning or working on at the moment.
 Check [Discussions](https://github.com/nuxt/nuxt/discussions) and [RFCs](https://github.com/nuxt/nuxt/discussions/categories/rfcs) for more upcoming features and ideas.
 ::
 
-Milestone    | Expected date | Notes                                                                  | Description
--------------|---------------|------------------------------------------------------------------------|-----------------------
-SEO & PWA    | 2025          | [nuxt/nuxt#18395](https://github.com/nuxt/nuxt/discussions/18395)      | Migrating from [nuxt-community/pwa-module](https://github.com/nuxt-community/pwa-module) for built-in SEO utils and service worker support
-Assets       | 2025          | [nuxt/nuxt#22012](https://github.com/nuxt/nuxt/discussions/22012)      | Allow developers and modules to handle loading third-party assets.
-Translations | -             | [nuxt/translations#4](https://github.com/nuxt/translations/discussions/4) ([request access](https://github.com/nuxt/nuxt/discussions/16054)) | A collaborative project for a stable translation process for Nuxt docs. Currently pending for ideas and documentation tooling support (content v2 with remote sources).
+| Milestone    | Expected date | Notes                                                              | Description                                                                                                                                |
+|--------------|---------------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| SEO & PWA    | 2025          | [nuxt/nuxt#18395](https://github.com/nuxt/nuxt/discussions/18395)  | Migrating from [nuxt-community/pwa-module](https://github.com/nuxt-community/pwa-module) for built-in SEO utils and service worker support |
+| Assets       | 2025          | [nuxt/nuxt#22012](https://github.com/nuxt/nuxt/discussions/22012)  | Allow developers and modules to handle loading third-party assets.                                                                         |
+| Translations | -             | [nuxt/nuxt.com#1711](https://github.com/nuxt/nuxt.com/issues/1711) | A collaborative project for a stable translation process for Nuxt docs. Currently pending for ideas and documentation tooling support.     |
 
 ## Core Modules Roadmap
 
 In addition to the Nuxt framework, there are modules that are vital for the ecosystem. Their status will be updated below.
 
-Module                                 | Status              | Nuxt Support | Repository | Description
----------------------------------------|---------------------|--------------|------------|-------------------
-[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)
-[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.
+| Module                                 | Status       | Nuxt Support | Repository                                      | Description                                                                                                                                                          |
+|----------------------------------------|--------------|--------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [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](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,24 +61,24 @@ 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/3.x/guide/going-further/nightly-release-channel).
 
-Release                    |                                                                                                                                                                               | Initial release       | End Of Life                  | Docs
--------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ---------------------------- | ---------------------------------------
-**5.x** (scheduled)        |                                                                                                                                                                               | Q4 2025 (estimated)   | TBA                          |  
-**4.x** (stable)           | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt latest version" src="https://flat.badgen.net/npm/v/nuxt?label=" class="not-prose"></a>         | 2025-07-16            | 6 months after 5.x release   | [nuxt.com](/docs/4.x)
-**3.x** (maintenance)      | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 3.x version" src="https://flat.badgen.net/npm/v/nuxt/3x?label=" class="not-prose"></a>         | 2022-11-16            | 2026-01-31                   | [nuxt.com](/docs/3.x)
-**2.x** (unsupported)      | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 2.x version" src="https://flat.badgen.net/npm/v/nuxt/2x?label=" class="not-prose"></a>         | 2018-09-21            | 2024-06-30                   | [v2.nuxt.com](https://v2.nuxt.com/docs)
-**1.x** (unsupported)      | <a href="https://www.npmjs.com/package/nuxt?activeTab=versions"><img alt="Nuxt 1.x version" src="https://flat.badgen.net/npm/v/nuxt/1x?label=" class="not-prose"></a>         | 2018-01-08            | 2019-09-21                   | &nbsp;
+| Release               |                                                                                                                                                                                                                                                    | Initial release     | End Of Life                | Docs                                                              |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------|-------------------------------------------------------------------|
+| **5.x** (scheduled)   |                                                                                                                                                                                                                                                    | Q1 2026 (estimated) | TBA                        | &nbsp;                                                            |
+| **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-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;                                                            |
 
 ### Support Status
 
-Status      | Description
-------------|----------------------------------------------------------------------------------
-Unsupported | This version is not maintained any more and will not receive security patches
-Maintenance | This version will only receive security patches
-Stable      | This version is being developed for and will receive security patches
-Development | This version could be unstable
-Scheduled   | This version does not exist yet but is planned
+| Status      | Description                                                                   |
+|-------------|-------------------------------------------------------------------------------|
+| Unsupported | This version is not maintained any more and will not receive security patches |
+| Maintenance | This version will only receive security patches                               |
+| Stable      | This version is being developed for and will receive security patches         |
+| Development | This version could be unstable                                                |
+| Scheduled   | This version does not exist yet but is planned                                |

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/3.bridge-composition-api.md

@@ -91,7 +91,7 @@ export default <Middleware> function (ctx) { }
 
 This was a type-helper stub function that is now removed.
 
-You may also keep using Nuxt 2-style plugins, by removing the function (as with [defineNuxtMiddleware](#definenuxtmiddleware)).
+You may also keep using Nuxt 2-style plugins, by removing the function (as with [defineNuxtMiddleware](/docs/3.x/bridge/bridge-composition-api#definenuxtmiddleware)).
 
 Remove the `defineNuxtPlugin` wrapper:
 
@@ -113,7 +113,7 @@ export default <Plugin> function (ctx, inject) {}
 While this example is valid, Nuxt 3 introduces a new defineNuxtPlugin function that has a slightly different signature.
 ::
 
-:ReadMore{link="/docs/guide/directory-structure/plugins#creating-plugins"}
+:ReadMore{link="/docs/3.x/directory-structure/plugins#creating-plugins"}
 
 ### `useRouter` and `useRoute`
 

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

@@ -39,14 +39,14 @@ export default defineNuxtRouteMiddleware((to) => {
 ```
 
 ::important
-Use of `defineNuxtRouteMiddleware` is not supported outside of the middleware directory.
+Use of `defineNuxtRouteMiddleware` is not supported outside of the `middleware` directory.
 ::
 
 ## definePageMeta
 
 You can also use [`definePageMeta`](/docs/3.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/5.nuxt3-compatible-api.md

@@ -204,4 +204,4 @@ export default defineNuxtConfig({
 })
 ```
 
-This will disable auto-imports completely but it's still possible to use [explicit imports](#explicit-imports) from `#imports`.
+This will disable auto-imports completely but it's still possible to use [explicit imports](/docs/3.x/bridge/nuxt3-compatible-api#explicit-imports) from `#imports`.

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/10.bundling.md

@@ -16,7 +16,7 @@ If you need to configure any of Nuxt's build tools, you can do so in your `nuxt.
 
 In addition, Nuxt ships with TypeScript support.
 
-:read-more{to="/docs/guide/concepts/typescript"}
+:read-more{to="/docs/3.x/guide/concepts/typescript"}
 
 ## Steps
 

package/7.migration/11.server.md

@@ -5,7 +5,7 @@ description: 'Learn how to migrate from Nuxt 2 to Nuxt 3 server.'
 
 In a built Nuxt 3 application, there is no runtime Nuxt dependency. That means your site will be highly performant, and ultra-slim. But it also means you can no longer hook into runtime Nuxt server hooks.
 
-:read-more{to="/docs/guide/concepts/server-engine"}
+:read-more{to="/docs/3.x/guide/concepts/server-engine"}
 
 ## Steps
 
@@ -13,5 +13,5 @@ In a built Nuxt 3 application, there is no runtime Nuxt dependency. That means y
 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/guide/directory-structure/server"}
-:read-more{to="/docs/guide/going-further/hooks#server-hooks-runtime"}
+:read-more{to="/docs/3.x/directory-structure/server"}
+:read-more{to="/docs/3.x/guide/going-further/hooks#server-hooks-runtime"}

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,14 +133,14 @@ 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/3.x/migration/module-authors) and [our module author guide](/docs/3.x/guide/going-further/modules).
+If you are a module author, you can check out [more information about module compatibility](/docs/3.x/migration/module-authors) and [our module author guide](/docs/3.x/guide/modules).
 ::
 
 ## Directory Changes
 
 The `static/` (for storing static assets) has been renamed to `public/`. You can either rename your `static` directory to `public`, or keep the name by setting `dir.public` in your `nuxt.config`.
 
-:read-more{to="/docs/guide/directory-structure/public"}
+:read-more{to="/docs/3.x/directory-structure/public"}
 
 ## TypeScript
 
@@ -163,13 +163,13 @@ Nuxt can type-check your app using [`vue-tsc`](https://github.com/vuejs/language
    ```
 
 1. Run `npx nuxt prepare` to generate `.nuxt/tsconfig.json`.
-1. Install Volar following the instructions in the [docs](/docs/3.x/getting-started/introduction#prerequisites).
+1. Install Volar following the instructions in the [docs](/docs/3.x/getting-started/installation#prerequisites).
 
 ## Vue Changes
 
 There are a number of changes to what is recommended Vue best practice, as well as a number of breaking changes between Vue 2 and 3.
 
-It is recommended to read the [Vue 3 migration guide](https://v3-migration.vuejs.org) and in particular the [breaking changes list](https://v3-migration.vuejs.org/breaking-changes).
+It is recommended to read the [Vue 3 migration guide](https://v3-migration.vuejs.org) and in particular the [breaking changes list](https://v3-migration.vuejs.org/breaking-changes/).
 
 It is not currently possible to use the [Vue 3 migration build](https://v3-migration.vuejs.org/migration-build.html) with Nuxt 3.
 

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/3.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/3.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.
@@ -17,7 +17,7 @@ Explore Nuxt 3 compatible modules.
 
 Nuxt 3 plugins are **not** fully backward compatible with Nuxt 2.
 
-:read-more{to="/docs/guide/directory-structure/plugins"}
+:read-more{to="/docs/3.x/directory-structure/plugins"}
 
 ### Vue Compatibility
 
@@ -78,7 +78,7 @@ Your module should work even if it's only added to [`buildModules`](/docs/3.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/3.x/guide/going-further/modules).
+Continue reading about Nuxt 3 modules in the [Modules Author Guide](/docs/3.x/guide/modules).
 ::
 
 ### Use TypeScript (Optional)

package/7.migration/4.meta.md

@@ -14,7 +14,7 @@ You can customize `title`, `titleTemplate`, `base`, `script`, `noscript`, `style
 Nuxt currently uses [`Unhead`](https://github.com/unjs/unhead) to manage your meta tags, but implementation details may change.
 ::
 
-:read-more{to="/docs/getting-started/seo-meta"}
+:read-more{to="/docs/3.x/getting-started/seo-meta"}
 
 ## Migration
 

package/7.migration/5.plugins-and-middleware.md

@@ -31,9 +31,9 @@ export default defineNuxtPlugin((nuxtApp) => {
 
 ::
 
-:read-more{to="/docs/guide/directory-structure/plugins"}
+:read-more{to="/docs/3.x/directory-structure/plugins"}
 
-::read-more{to="/docs/api/composables/use-nuxt-app"}
+::read-more{to="/docs/3.x/api/composables/use-nuxt-app"}
 Read more about the format of `nuxtApp`.
 ::
 
@@ -72,7 +72,7 @@ Much like Nuxt 2, route middleware placed in your `~/middleware` folder is autom
 
 `navigateTo` is one of a number of route helper functions.
 
-:read-more{to="/docs/guide/directory-structure/middleware"}
+:read-more{to="/docs/3.x/directory-structure/middleware"}
 
 ### Migration
 

package/7.migration/6.pages-and-layouts.md

@@ -13,9 +13,9 @@ If you don't have an `app.vue` file in your source directory, Nuxt will use its
 
 This file is a great place to put any custom code that needs to be run once when your app starts up, as well as any components that are present on every page of your app. For example, if you only have one layout, you can move this to `app.vue` instead.
 
-:read-more{to="/docs/guide/directory-structure/app"}
+:read-more{to="/docs/3.x/directory-structure/app"}
 
-:link-example{to="/docs/examples/hello-world"}
+:link-example{to="/docs/3.x/examples/hello-world"}
 
 ### Migration
 
@@ -84,13 +84,13 @@ In Nuxt 2, you will have defined any nested routes (with parent and child compon
 
 If you were passing a custom page key or keep-alive props to `<Nuxt>`, you will now use `definePageMeta` to set these options.
 
-:read-more{to="/docs/guide/directory-structure/pages#special-metadata"}
+:read-more{to="/docs/3.x/directory-structure/pages#special-metadata"}
 
 ### Page and Layout Transitions
 
 If you have been defining transitions for your page or layout directly in your component options, you will now need to use `definePageMeta` to set the transition. Since Vue 3, [-enter and -leave CSS classes have been renamed](https://v3-migration.vuejs.org/breaking-changes/transition.html). The `style` prop from `<Nuxt>` no longer applies to transition when used on `<slot>`, so move the styles to your `-active` class.
 
-:read-more{to="/docs/getting-started/transitions"}
+:read-more{to="/docs/3.x/getting-started/transitions"}
 
 ### Migration
 
@@ -190,7 +190,7 @@ Most of the syntax and functionality are the same for the global [NuxtLink](/doc
 
 `<NuxtLink>` is now a drop-in replacement for _all_ links, even external ones. You can read more about it, and how to extend it to provide your own link component.
 
-:read-more{to="/docs/api/components/nuxt-link"}
+:read-more{to="/docs/3.x/api/components/nuxt-link"}
 
 ## Programmatic Navigation
 

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

@@ -67,7 +67,7 @@ Despite the names, [`useFetch`](/docs/3.x/api/composables/use-fetch) is not a di
 
 ## `head`
 
-:read-more{to="/docs/migration/meta"}
+:read-more{to="/docs/3.x/migration/meta"}
 
 ## `key`
 
@@ -91,7 +91,7 @@ You can now define a key within the [`definePageMeta`](/docs/3.x/api/utils/defin
 
 ## `layout`
 
-:read-more{to="/docs/migration/pages-and-layouts"}
+:read-more{to="/docs/3.x/migration/pages-and-layouts"}
 
 ## `loading`
 
@@ -99,11 +99,11 @@ This feature is not yet supported in Nuxt 3.
 
 ## `middleware`
 
-:read-more{to="/docs/migration/plugins-and-middleware"}
+:read-more{to="/docs/3.x/migration/plugins-and-middleware"}
 
 ## `scrollToTop`
 
-This feature is not yet supported in Nuxt 3. If you want to overwrite the default scroll behavior of `vue-router`, you can do so in `~/app/router.options.ts` (see [docs](/docs/3.x/guide/recipes/custom-routing#router-options)) for more info.
+This feature is not yet supported in Nuxt 3. If you want to overwrite the default scroll behavior of `vue-router`, you can do so in an `~/app/router.options.ts` (see [docs](/docs/3.x/guide/recipes/custom-routing#router-options)) for more info.
 Similar to `key`, specify it within the [`definePageMeta`](/docs/3.x/api/utils/define-page-meta) compiler macro.
 
 ```diff [pages/index.vue]
@@ -120,11 +120,11 @@ Similar to `key`, specify it within the [`definePageMeta`](/docs/3.x/api/utils/d
 
 ## `transition`
 
-:read-more{to="/docs/getting-started/transitions"}
+:read-more{to="/docs/3.x/getting-started/transitions"}
 
 ## `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 [pages/users/[id\\].vue]
 - <script>

package/7.migration/8.runtime-config.md

@@ -9,7 +9,7 @@ When referencing these variables within your components, you will have to use th
 
 In the `server/` portion of your app, you can use [`useRuntimeConfig`](/docs/3.x/api/composables/use-runtime-config) without any import.
 
-:read-more{to="/docs/guide/going-further/runtime-config"}
+:read-more{to="/docs/3.x/guide/going-further/runtime-config"}
 
 ## Migration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs",
-  "version": "3.20.2",
+  "version": "3.21.1",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",

package/3.guide/4.going-further/1.features.md

@@ -1,103 +0,0 @@
----
-title: "Features"
-description: "Enable or disable optional Nuxt features to unlock new possibilities."
----
-
-Some features of Nuxt are available on an opt-in basis, or can be disabled based on your needs.
-
-## `features`
-
-### inlineStyles
-
-Inlines styles when rendering HTML. This is currently available only when using Vite.
-
-You can also pass a function that receives the path of a Vue component and returns a boolean indicating whether to inline the styles for that component.
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
-  features: {
-    inlineStyles: false, // or a function to determine inlining
-  },
-})
-```
-
-### noScripts
-
-Disables rendering of Nuxt scripts and JS resource hints. Can also be configured granularly within `routeRules`.
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
-  features: {
-    noScripts: true,
-  },
-})
-```
-
-## `future`
-
-There is also a `future` namespace for early opting-in to new features that will become default in a future (possibly major) version of the framework.
-
-### compatibilityVersion
-
-::important
-This configuration option is available in Nuxt v3.12+. Please note, that for now, you need to define the compatibility version in each layer that opts into Nuxt 4 behavior. This will not be required after Nuxt 4 is released.
-::
-
-This enables early access to Nuxt features or flags.
-
-Setting `compatibilityVersion` to `4` changes defaults throughout your
-Nuxt configuration to opt-in to Nuxt v4 behaviour, but you can granularly re-enable Nuxt v3 behaviour
-when testing (see example). Please file issues if so, so that we can
-address in Nuxt or in the ecosystem.
-
-```ts
-export default defineNuxtConfig({
-  future: {
-    compatibilityVersion: 4,
-  },
-  // To re-enable _all_ Nuxt v3 behaviour, set the following options:
-  srcDir: '.',
-  dir: {
-    app: 'app',
-  },
-  experimental: {
-    scanPageMeta: 'after-resolve',
-    sharedPrerenderData: false,
-    compileTemplate: true,
-    resetAsyncDataToUndefined: true,
-    templateUtils: true,
-    relativeWatchPaths: true,
-    normalizeComponentNames: false,
-    defaults: {
-      useAsyncData: {
-        deep: true,
-      },
-    },
-  },
-  features: {
-    inlineStyles: true,
-  },
-  unhead: {
-    renderSSRHeadOptions: {
-      omitLineBreaks: false,
-    },
-  },
-})
-```
-
-### typescriptBundlerResolution
-
-This enables 'Bundler' module resolution mode for TypeScript, which is the recommended setting
-for frameworks like Nuxt and [Vite](https://vite.dev/guide/performance.html#reduce-resolve-operations).
-
-It improves type support when using modern libraries with `exports`.
-
-See [the original TypeScript pull request](https://github.com/microsoft/TypeScript/pull/51669).
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
-  future: {
-    typescriptBundlerResolution: true,
-  },
-})
-```