@nuxt/docs-nightly 4.5.1-29752449.30d24817 → 4.5.2-2610052030-052d82e

package/4.api/6.advanced/1.hooks.md

@@ -3,7 +3,7 @@ title: 'Lifecycle Hooks'
 description: Nuxt provides a powerful hooking system to expand almost every aspect using hooks.
 ---
 
-:read-more{to="/docs/4.x/guide/going-further/hooks"}
+:read-more{to="/docs/guide/going-further/hooks"}
 
 ## App Hooks (Runtime)
 
@@ -30,7 +30,7 @@ Check the [app source code](https://github.com/nuxt/nuxt/blob/main/packages/nuxt
 | `page:loading:end`           | -                   | Client          | Called after `page:finish`                                                                                                                                                            |
 | `page:transition:finish`     | `pageComponent?`    | Client          | After page transition [onAfterLeave](https://vuejs.org/guide/built-ins/transition#javascript-hooks) event.                                                                            |
 | `dev:ssr-logs`               | `logs`              | Client          | Called with an array of server-side logs that have been passed to the client (if `features.devLogs` is enabled).                                                                      |
-| `page:view-transition:start` | `transition`        | Client          | Called after `document.startViewTransition` is called when [experimental viewTransition support is enabled](/docs/4.x/getting-started/transitions#view-transitions-api-experimental). The `transition` argument is a [`ViewTransition`](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition) object with a `types` property ([`ViewTransitionTypeSet`](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransitionTypeSet)) that can be read or modified. |
+| `page:view-transition:start` | `transition`        | Client          | Called after `document.startViewTransition` is called when [experimental viewTransition support is enabled](/docs/getting-started/transitions#view-transitions-api-experimental). The `transition` argument is a [`ViewTransition`](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition) object with a `types` property ([`ViewTransitionTypeSet`](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransitionTypeSet)) that can be read or modified. |
 
 ## Nuxt Hooks (Build Time)
 
@@ -44,9 +44,11 @@ Check the [schema source code](https://github.com/nuxt/nuxt/blob/main/packages/s
 | `restart`                   | `{ hard?: boolean }`                                     | To be called to restart the current Nuxt instance.                                                                                                                                                                                                                                           |
 | `modules:before`            | -                                                        | Called during Nuxt initialization, before installing user modules.                                                                                                                                                                                                                           |
 | `modules:done`              | -                                                        | Called during Nuxt initialization, after installing user modules.                                                                                                                                                                                                                            |
+| `module:before`             | `module`                                                 | Called immediately before each individual module is set up.                                                                                                                                                                                                                                  |
+| `module:done`               | `module`                                                 | Called immediately after each individual module has been set up, including how long it took.                                                                                                                                                                                                  |
 | `app:resolve`               | `app`                                                    | Called after resolving the `app` instance.                                                                                                                                                                                                                                                   |
 | `app:templates`             | `app`                                                    | Called during `NuxtApp` generation, to allow customizing, modifying or adding new files to the build directory (either virtually or to written to `.nuxt`).                                                                                                                                  |
-| `app:templatesGenerated`    | `app`                                                    | Called after templates are compiled into the [virtual file system](/docs/4.x/directory-structure/nuxt) (vfs).                                                                                                                                                                                |
+| `app:templatesGenerated`    | `app`                                                    | Called after templates are compiled into the [virtual file system](/docs/directory-structure/nuxt) (vfs).                                                                                                                                                                                |
 | `build:before`              | -                                                        | Called before Nuxt bundle builder.                                                                                                                                                                                                                                                           |
 | `build:done`                | -                                                        | Called after Nuxt bundle builder is complete.                                                                                                                                                                                                                                                |
 | `build:manifest`            | `manifest`                                               | Called during the manifest build by Vite and webpack. This allows customizing the manifest that Nitro will use to render `<script>` and `<link>` tags in the final HTML.                                                                                                                     |
@@ -55,6 +57,7 @@ Check the [schema source code](https://github.com/nuxt/nuxt/blob/main/packages/s
 | `pages:extend`              | `pages`                                                  | Called after page routes are scanned from the file system.                                                                                                                                                                                                                                   |
 | `pages:resolved`            | `pages`                                                  | Called after page routes have been augmented with scanned metadata.                                                                                                                                                                                                                          |
 | `pages:routerOptions`       | `{ files: Array<{ path: string, optional?: boolean }> }` | Called when resolving `router.options` files. Later items in the array override earlier ones.                                                                                                                                                                                                |
+| `server:routes`             | `routes`, `context`                                      | Called when Nuxt needs the full set of route handlers the server will serve, so that it can type `$fetch` and `useFetch` against them.                                                                                                                                                        |
 | `server:devHandler`         | `handler`                                                | Called when the dev middleware is being registered on the Nitro dev server.                                                                                                                                                                                                                  |
 | `imports:sources`           | `presets`                                                | Called at setup allowing modules to extend sources.                                                                                                                                                                                                                                          |
 | `imports:extend`            | `imports`                                                | Called at setup allowing modules to extend imports.                                                                                                                                                                                                                                          |

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

@@ -116,13 +116,11 @@ NUXT_APP_BASE_URL=./ npm run generate
 ```
 
 ```ts
-// Option 2: Nitro runtime config
+// Option 2: Runtime config
 export default defineNuxtConfig({
-  nitro: {
-    runtimeConfig: {
-      app: {
-        baseURL: './',
-      },
+  runtimeConfig: {
+    app: {
+      baseURL: './',
     },
   },
 })
@@ -329,13 +327,13 @@ Customize Nuxt Teleport element tag.
 
 Default values for view transitions.
 
-This only has an effect when **experimental** support for View Transitions is [enabled in your nuxt.config file](/docs/4.x/getting-started/transitions#view-transitions-api-experimental).
+This only has an effect when **experimental** support for View Transitions is [enabled in your nuxt.config file](/docs/getting-started/transitions#view-transitions-api-experimental).
 This can be overridden with `definePageMeta` on an individual page.
 
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt View Transition API docs](/docs/4.x/getting-started/transitions#view-transitions-api-experimental)
+**See**: [Nuxt View Transition API docs](/docs/getting-started/transitions#view-transitions-api-experimental)
 
 ## appConfig
 
@@ -528,7 +526,7 @@ Any components in the directories configured here can be used throughout your pa
 }
 ```
 
-**See**: [`app/components/` directory documentation](/docs/4.x/directory-structure/app/components)
+**See**: [`app/components/` directory documentation](/docs/directory-structure/app/components)
 
 ## css
 
@@ -742,7 +740,7 @@ Configure shared esbuild options used within Nuxt and passed to other builders,
 
 ## experimental
 
-::read-more{to="/docs/4.x/guide/going-further/experimental-features"}
+::read-more{to="/docs/guide/going-further/experimental-features"}
 Learn more about Nuxt's experimental features.
 ::
 
@@ -776,13 +774,13 @@ The extensions that should be resolved by the Nuxt resolver.
 
 ## features
 
-::read-more{to="/docs/4.x/guide/going-further/features#features"}
+::read-more{to="/docs/guide/going-further/features#features"}
 Learn more about Nuxt's opt-in features.
 ::
 
 ## future
 
-::read-more{to="/docs/4.x/guide/going-further/features#features"}
+::read-more{to="/docs/guide/going-further/features#features"}
 Learn more about opting-in to new features that will become default in a future (possibly major) version of the framework.
 ::
 
@@ -859,7 +857,7 @@ Any file in `app/pages/`, `app/layouts/`, `app/middleware/`, and `public/` direc
 
 Configure how Nuxt auto-imports composables into your application.
 
-**See**: [Nuxt documentation](/docs/4.x/directory-structure/app/composables)
+**See**: [Nuxt documentation](/docs/directory-structure/app/composables)
 
 ### `dirs`
 
@@ -1039,7 +1037,7 @@ 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 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"}
+::read-more{to="/docs/guide/modules/recipes-basics#add-keyed-functions"}
 Learn more about keyed functions.
 ::
 
@@ -1181,7 +1179,7 @@ and these plugins do not need to be listed in `nuxt.config` unless you
 need to customize their order. All plugins are deduplicated by their src path.
 ::
 
-**See**: [`app/plugins/` directory documentation](/docs/4.x/directory-structure/app/plugins)
+**See**: [`app/plugins/` directory documentation](/docs/directory-structure/app/plugins)
 
 **Example**:
 ```ts
@@ -1317,6 +1315,8 @@ Specify the server builder to use for bundling the server part of your applicati
 
 By default, Nuxt uses `@nuxt/nitro-server`, which provides standalone Nitro integration. This architecture allows for different Nitro integration patterns, such as using Nitro as a Vite plugin (with the Vite Environment API).
 
+`"nitro"` and `"vite"` are shorthands for `@nuxt/nitro-server` and `@nuxt/vite-server`. The latter is experimental and implemented with Vite alone: with `ssr: false` it produces a static SPA, and with SSR enabled it builds a server from the Nuxt SSR renderer whose entry exports a web-standard `{ fetch }` (`.output/server/index.mjs` serves the static output in front of it, and `nuxt preview` runs it). Every dependency is bundled into that output, so it deploys without `node_modules`. `nuxt generate` crawls that server at the end of the build and writes a static `.output/public`. It ships no server runtime, so server routes, route rules other than `prerender`, inlined styles and server components are unavailable, and modules that need a server will not work.
+
 - **Type**: `string | { bundle: (nuxt: Nuxt) => Promise<void> }`
 - **Default:** `"@nuxt/nitro-server"`
 
@@ -1342,7 +1342,7 @@ Each handler accepts the following options:
 
 - **Type**: `array`
 
-**See**: [`server/` directory documentation](/docs/4.x/directory-structure/server)
+**See**: [`server/` directory documentation](/docs/directory-structure/server)
 
 ::callout
 **Note**: Files from `server/api`, `server/middleware` and `server/routes` will be automatically registered by Nuxt.
@@ -1499,6 +1499,12 @@ You can use `github:`, `gitlab:`, `bitbucket:` or `https://` to extend from a re
 
 Configuration for Nuxt's TypeScript integration.
 
+### `appTsConfig`
+
+You can extend the generated `.nuxt/tsconfig.app.json` (and legacy `.nuxt/tsconfig.json`) TypeScript configuration using this option. Options set here take precedence over `tsConfig`.
+
+**See**: [tsconfig.json information](/docs/directory-structure/tsconfig)
+
 ### `builder`
 
 Which builder types to include for your project.
@@ -1547,13 +1553,19 @@ Include parent workspace in the Nuxt project. Mostly useful for themes and modul
 
 You can extend the generated `.nuxt/tsconfig.node.json` TypeScript configuration using this option.
 
-**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
+**See**: [tsconfig.json information](/docs/directory-structure/tsconfig)
+
+### `serverTsConfig`
+
+You can extend the generated `.nuxt/tsconfig.server.json` TypeScript configuration using this option. Options set here take precedence over `tsConfig`.
+
+**See**: [tsconfig.json information](/docs/directory-structure/tsconfig)
 
 ### `sharedTsConfig`
 
 You can extend the generated `.nuxt/tsconfig.shared.json` TypeScript configuration using this option.
 
-**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
+**See**: [tsconfig.json information](/docs/directory-structure/tsconfig)
 
 ### `shim`
 
@@ -1576,9 +1588,9 @@ TypeScript comes with certain checks to give you more safety and analysis of you
 
 ### `tsConfig`
 
-You can extend the generated `.nuxt/tsconfig.app.json` TypeScript configuration using this option.
+You can extend the generated tsconfig files with shared options using this option. `compilerOptions` apply to all generated tsconfigs (`.nuxt/tsconfig.app.json`, `.nuxt/tsconfig.server.json`, `.nuxt/tsconfig.node.json` and `.nuxt/tsconfig.shared.json`), while `include`, `exclude` and `vueCompilerOptions` apply only to `.nuxt/tsconfig.app.json` (and the legacy `.nuxt/tsconfig.json`). Two groups of `compilerOptions` are exceptions: DOM- and Vue-specific options (such as `lib`, `jsx` and `jsxImportSource`) apply only to `.nuxt/tsconfig.app.json`, and `types`, `paths` and `noEmit` are managed by Nuxt per context, so they cannot be set globally for the `node`, `shared` and `server` tsconfigs. Use `appTsConfig`, `serverTsConfig`, `nodeTsConfig` or `sharedTsConfig` for context-specific overrides; they take precedence over this option.
 
-**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
+**See**: [tsconfig.json information](/docs/directory-structure/tsconfig)
 
 ### `typeCheck`
 
@@ -1589,7 +1601,18 @@ If set to true, this will type check in development. You can restrict this to bu
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt TypeScript docs](/docs/4.x/guide/concepts/typescript)
+**See**: [Nuxt TypeScript docs](/docs/guide/concepts/typescript)
+
+## typesDir
+
+Define the directory where generated types and `tsconfig.json` files will be placed.
+
+This defaults to your `buildDir`, and is separate from it so that the configurations referenced by your project `tsconfig.json` stay in place even when Nuxt builds elsewhere (as it does when building a project that has already been run in development).
+
+If a relative path is specified, it will be relative to your `rootDir`.
+
+- **Type**: `string`
+- **Default:** `"/<rootDir>/.nuxt"`
 
 ## unhead
 

package/4.api/index.md

@@ -7,25 +7,25 @@ surround: false
 ---
 
 ::card-group
-  ::card{icon="i-lucide-box" title="Components" to="/docs/4.x/api/components/client-only"}
+  ::card{icon="i-lucide-box" title="Components" to="/docs/api/components/client-only"}
   Explore Nuxt built-in components for pages, layouts, head, and more.
   ::
-  ::card{icon="i-lucide-arrow-left-right" title="Composables" to="/docs/4.x/api/composables/use-app-config"}
+  ::card{icon="i-lucide-arrow-left-right" title="Composables" to="/docs/api/composables/use-app-config"}
   Discover Nuxt composable functions for data-fetching, head management and more.
   ::
-  ::card{icon="i-lucide-square-function" title="Utils" to="/docs/4.x/api/utils/dollarfetch"}
+  ::card{icon="i-lucide-square-function" title="Utils" to="/docs/api/utils/dollarfetch"}
   Learn about Nuxt utility functions for navigation, error handling and more.
   ::
-  ::card{icon="i-lucide-square-terminal" title="Commands" to="/docs/4.x/api/commands/add"}
+  ::card{icon="i-lucide-square-terminal" title="Commands" to="/docs/api/commands/add"}
   List of Nuxt CLI commands to init, analyze, build, and preview your application.
   ::
-  ::card{icon="i-lucide-package" title="Nuxt Kit" to="/docs/4.x/api/kit/modules"}
+  ::card{icon="i-lucide-package" title="Nuxt Kit" to="/docs/api/kit/modules"}
   Understand Nuxt Kit utilities to create modules and control Nuxt.
   ::
-  ::card{icon="i-lucide-brain" title="Advanced" to="/docs/4.x/api/advanced/hooks"}
+  ::card{icon="i-lucide-brain" title="Advanced" to="/docs/api/advanced/hooks"}
   Go deep in Nuxt internals with Nuxt lifecycle hooks.
   ::
-  ::card{icon="i-lucide-cog" title="Nuxt Configuration" to="/docs/4.x/api/nuxt-config"}
+  ::card{icon="i-lucide-cog" title="Nuxt Configuration" to="/docs/api/nuxt-config"}
   Explore all Nuxt configuration options to customize your application.
   ::
 ::

package/5.community/2.getting-help.md

@@ -37,7 +37,7 @@ And finally, just ask the question! There's no need to [ask permission to ask a
 
 Something isn't working the way that the docs say that it should. You're not sure if it's a bug. You've searched through the [open issues](https://github.com/nuxt/nuxt/issues) and [discussions](https://github.com/nuxt/nuxt/discussions) but you can't find anything. (if there is a closed issue, please create a new one)
 
-We recommend taking a look at [how to report bugs](/docs/4.x/community/reporting-bugs). Nuxt is still in active development, and every issue helps make it better.
+We recommend taking a look at [how to report bugs](/docs/community/reporting-bugs). Nuxt is still in active development, and every issue helps make it better.
 
 ## "I need professional help"
 

package/5.community/3.reporting-bugs.md

@@ -12,7 +12,7 @@ Here are a few key steps.
 
 ## Is It Really a Bug?
 
-Consider if you're looking to get help with something, or whether you think there's a bug with Nuxt itself. If it's the former, we'd love to help you - but the best way to do that is through [asking for help](/docs/4.x/community/getting-help) rather than reporting a bug.
+Consider if you're looking to get help with something, or whether you think there's a bug with Nuxt itself. If it's the former, we'd love to help you - but the best way to do that is through [asking for help](/docs/community/getting-help) rather than reporting a bug.
 
 ## Search the Issues
 

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/modules/ecosystem) 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/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
@@ -24,7 +24,7 @@ Check out the issues and discussions for the project you want to help. For examp
 
 Thank you for taking the time to create an issue! ❤️
 
-* **Reporting bugs**: Check out [our guide](/docs/4.x/community/reporting-bugs) for some things to do before opening an issue.
+* **Reporting bugs**: Check out [our guide](/docs/community/reporting-bugs) for some things to do before opening an issue.
 
 * **Feature requests**: Check that there is not an existing issue or discussion covering the scope of the feature you have in mind. If the feature is to another part of the Nuxt ecosystem (such as a module), please consider raising a feature request there first. If the feature you have in mind is general or the API is not entirely clear, consider opening a discussion in the **Ideas** section to discuss with the community first.
 
@@ -42,7 +42,7 @@ If you're working on a feature, then we ask that you **open a feature request is
 
 For typo fixes, it's recommended to batch multiple typo fixes into one pull request to maintain a cleaner commit history.
 
-For bigger changes to Nuxt itself, we recommend that you first [create a Nuxt module](/docs/4.x/community/contribution#create-a-module) and implement the feature there. This allows for quick proof-of-concept. You can then [create an RFC](/docs/4.x/community/contribution#make-an-rfc) in the form of a discussion. As users adopt it and you gather feedback, it can then be refined and either added to Nuxt core or continue as a standalone module.
+For bigger changes to Nuxt itself, we recommend that you first [create a Nuxt module](/docs/community/contribution#create-a-module) and implement the feature there. This allows for quick proof-of-concept. You can then [create an RFC](/docs/community/contribution#make-an-rfc) in the form of a discussion. As users adopt it and you gather feedback, it can then be refined and either added to Nuxt core or continue as a standalone module.
 
 #### Commit Conventions
 
@@ -58,7 +58,7 @@ If you are working in a project with a monorepo, like `nuxt/nuxt`, ensure that y
 
 If you don't know how to send a pull request, we recommend reading [the guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
 
-When sending a pull request, make sure your PR's title also follows the [Commit Convention](/docs/4.x/community/contribution#commit-conventions).
+When sending a pull request, make sure your PR's title also follows the [Commit Convention](/docs/community/contribution#commit-conventions).
 
 If your PR fixes or resolves existing issues, please make sure you mention them in the PR description.
 
@@ -100,13 +100,13 @@ 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/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/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).
+If you need help while building it, feel free to [check in with us](/docs/community/getting-help).
 
 ### Make an RFC
 
-We highly recommend [creating a module](/docs/4.x/community/contribution#create-a-module) first to test out big new features and gain community adoption.
+We highly recommend [creating a module](/docs/community/contribution#create-a-module) first to test out big new features and gain community adoption.
 
 If you have done this already, or it's not appropriate to create a new module, then please start by creating a new discussion. Make sure it explains your thinking as clearly as possible. Include code examples or function signatures for new APIs. Reference existing issues or pain points with examples.
 
@@ -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/modules) for more information.
+Modules should follow the [Nuxt module template](https://github.com/nuxt/starter/tree/module). See [module guide](/docs/guide/modules) for more information.
 
 #### Use Core `unjs/` Libraries
 
@@ -139,7 +139,7 @@ We recommend the following libraries which are used throughout the ecosystem:
 
 #### Use ESM Syntax and Default to `type: module`
 
-Most of the Nuxt ecosystem can consume ESM directly. In general we advocate that you avoid using CJS-specific code, such as `__dirname` and `require` statements. You can [read more about ESM](/docs/4.x/guide/concepts/esm).
+Most of the Nuxt ecosystem can consume ESM directly. In general we advocate that you avoid using CJS-specific code, such as `__dirname` and `require` statements. You can [read more about ESM](/docs/guide/concepts/esm).
 
 #### What's Corepack
 
@@ -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`, `bun run lint --fix`, or `deno 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/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.
 
@@ -256,7 +256,9 @@ Do not use backticks for names of tools, projects, or general concepts (use _Vit
 
 ### Links
 
-* When linking to other documentation pages, use relative paths without the domain: `/docs/4.x/getting-started/installation` rather than `https://nuxt.com/docs/4.x/getting-started/installation`.
+* When linking to other documentation pages, use relative paths without the domain or a version segment: `/docs/getting-started/installation` rather than `/docs/4.x/getting-started/installation` or `https://nuxt.com/docs/4.x/getting-started/installation`. nuxt.com inserts the version segment of the branch the page was built from, so the same link resolves correctly on every version and docs changes can be cherry-picked between branches unchanged.
+
+* Only write a version segment when you deliberately mean _another_ version's docs (the release table in the roadmap, for example). In that case use the full URL, `https://nuxt.com/docs/3.x/getting-started/introduction`, so the intent is obvious in review.
 
 * When linking to external resources, link to the final URL rather than one that redirects. You can check with:
 
@@ -313,6 +315,6 @@ We aim for a tone that is friendly and professional. Write directly to the reade
 
   To find the version, check `@since` in JSDoc in the source, the [release notes](https://github.com/nuxt/nuxt/releases), or the [Nuxt blog](https://nuxt.com/blog).
 
-::read-more{to="/docs/4.x/community/framework-contribution#documentation-guide"}
+::read-more{to="/docs/community/framework-contribution#documentation-guide"}
 Learn how to contribute to the documentation.
 ::

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

@@ -4,7 +4,7 @@ navigation.icon: i-lucide-github
 description: Some specific points about contributions to the framework repository.
 ---
 
-Once you've read the [general contribution guide](/docs/4.x/community/contribution), here are some specific points to make about contributions to the [`nuxt/nuxt`](https://github.com/nuxt/nuxt) repository.
+Once you've read the [general contribution guide](/docs/community/contribution), here are some specific points to make about contributions to the [`nuxt/nuxt`](https://github.com/nuxt/nuxt) repository.
 
 ## Monorepo Guide
 
@@ -42,7 +42,7 @@ To contribute to Nuxt, you need to set up a local environment.
     git checkout -b my-new-branch
     ```
 
-Then, test your changes against the [playground](/docs/4.x/community/framework-contribution#playground) and [test](/docs/4.x/community/framework-contribution#testing) your changes before submitting a pull request.
+Then, test your changes against the [playground](/docs/community/framework-contribution#playground) and [test](/docs/community/framework-contribution#testing) your changes before submitting a pull request.
 
 ### Playground
 
@@ -88,7 +88,7 @@ If there are still errors left, you must correct them manually.
 If you are adding a new feature or refactoring or changing the behavior of Nuxt in any other manner, you'll likely want to document the changes. Please include any changes to the docs in the same PR. You don't have to write documentation up on the first commit (but please do so as soon as your pull request is mature enough).
 
 ::important
-Make sure to make changes according to the [Documentation Style Guide](/docs/4.x/community/contribution#documentation-style-guide).
+Make sure to make changes according to the [Documentation Style Guide](/docs/community/contribution#documentation-style-guide).
 ::
 
 ### Final Checklist
@@ -100,7 +100,7 @@ When submitting your PR, there is a simple template that you have to fill out. P
 If you spot an area where we can improve documentation or error messages, please do open a PR - even if it's just to fix a typo!
 
 ::important
-Make sure to make changes according to the [Documentation Style Guide](/docs/4.x/community/contribution#documentation-style-guide).
+Make sure to make changes according to the [Documentation Style Guide](/docs/community/contribution#documentation-style-guide).
 ::
 
 ### Quick Edits

package/5.community/6.roadmap.md

@@ -41,7 +41,7 @@ In addition to the Nuxt framework, there are modules that are vital for the ecos
 | Module                                 | Status       | Nuxt Support | Repository                                      | Description                                                                                                                                                          |
 |----------------------------------------|--------------|--------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | 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)).        |
+| [a11y](https://github.com/nuxt/a11y)   | Public Alpha | 4.x, 5.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)).        |
 
 ## Release Cycle
 
@@ -59,15 +59,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 (bug fixes and security patches) until the end of July 2026.
+Nuxt 3 reached end of life on 31 July 2026 and no longer receives bug fixes or security patches. If you are still on Nuxt 3, follow the [upgrade guide](/docs/getting-started/upgrade) to move to Nuxt 4.
 
-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).
+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/guide/going-further/nightly-release-channel).
 
 | Release               |                                                                                                                                                                                                                                                    | Initial release     | End Of Life                | Docs                                                              |
 |-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------|-------------------------------------------------------------------|
-| **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-07-31                 | [nuxt.com](/docs/3.x/getting-started/introduction)                |
+| **5.x** (scheduled)   |                                                                                                                                                                                                                                                    | Q4 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](https://nuxt.com/docs/4.x/getting-started/introduction) |
+| **3.x** (unsupported) | <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](https://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/6.bridge/1.overview.md

@@ -4,11 +4,11 @@ description: Reduce the differences with Nuxt 3 and reduce the burden of migrati
 ---
 
 ::note
-If you're starting a fresh Nuxt 3 project, please skip this section and go to [Nuxt 3 Installation](/docs/4.x/getting-started/introduction).
+If you're starting a fresh Nuxt 3 project, please skip this section and go to [Nuxt 3 Installation](/docs/getting-started/introduction).
 ::
 
 ::warning
-Nuxt Bridge provides identical features to Nuxt 3 ([docs](/docs/4.x/guide/concepts/auto-imports)) but there are some limitations, notably that [`useAsyncData`](/docs/4.x/api/composables/use-async-data) and [`useFetch`](/docs/4.x/api/composables/use-fetch) composables are not available. Please read the rest of this page for details.
+Nuxt Bridge provides identical features to Nuxt 3 ([docs](/docs/guide/concepts/auto-imports)) but there are some limitations, notably that [`useAsyncData`](/docs/api/composables/use-async-data) and [`useFetch`](/docs/api/composables/use-fetch) composables are not available. Please read the rest of this page for details.
 ::
 
 Bridge is a forward-compatibility layer that allows you to experience many of the new Nuxt 3 features by simply installing and enabling a Nuxt module.
@@ -88,7 +88,7 @@ deno add -D npm:@nuxt/bridge npm:nuxi
 
 Please make sure to avoid any CommonJS syntax such as `module.exports`, `require` or `require.resolve` in your config file. It will soon be deprecated and unsupported.
 
-You can use static `import`, dynamic `import()` and `export default` instead. Using TypeScript by renaming to [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) is also possible and recommended.
+You can use static `import`, dynamic `import()` and `export default` instead. Using TypeScript by renaming to [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) is also possible and recommended.
 
 ```ts [nuxt.config.ts]
 import { defineNuxtConfig } from '@nuxt/bridge'
@@ -124,22 +124,22 @@ Try running `nuxt2` once here. You will see that the application works as before
 With Nuxt Bridge, the migration to Nuxt 3 can proceed in steps.
 The below `Upgrade Steps` does not need to be done all at once.
 
-- [TypeScript](/docs/4.x/bridge/typescript)
+- [TypeScript](/docs/bridge/typescript)
 
-- [Migrate Legacy Composition API](/docs/4.x/bridge/bridge-composition-api)
+- [Migrate Legacy Composition API](/docs/bridge/bridge-composition-api)
 
-- [Plugins and Middleware](/docs/4.x/bridge/plugins-and-middleware)
+- [Plugins and Middleware](/docs/bridge/plugins-and-middleware)
 
-- [Migrate New Composition API](/docs/4.x/bridge/nuxt3-compatible-api)
+- [Migrate New Composition API](/docs/bridge/nuxt3-compatible-api)
 
-- [Meta Tags](/docs/4.x/bridge/meta)
+- [Meta Tags](/docs/bridge/meta)
 
-- [Runtime Config](/docs/4.x/bridge/runtime-config)
+- [Runtime Config](/docs/bridge/runtime-config)
 
-- [Nitro](/docs/4.x/bridge/nitro)
+- [Nitro](/docs/bridge/nitro)
 
-- [Vite](/docs/4.x/bridge/vite)
+- [Vite](/docs/bridge/vite)
 
 ## Migrate from CommonJS to ESM
 
-Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/docs/4.x/guide/concepts/esm) for more info and upgrading.
+Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/docs/guide/concepts/esm) for more info and upgrading.

package/6.bridge/2.typescript.md

@@ -37,7 +37,7 @@ If you are using TypeScript, you can edit your `tsconfig.json` to benefit from a
 ::note
 As `.nuxt/tsconfig.json` is generated and not checked into version control, you'll need to generate that file before running your tests. Add `nuxi prepare` as a step before your tests, otherwise you'll see `TS5083: Cannot read file '~/.nuxt/tsconfig.json'`
 
-For modern Nuxt projects, we recommend using [TypeScript project references](/docs/4.x/directory-structure/tsconfig) instead of directly extending `.nuxt/tsconfig.json`.
+For modern Nuxt projects, we recommend using [TypeScript project references](/docs/directory-structure/tsconfig) instead of directly extending `.nuxt/tsconfig.json`.
 ::
 
 ::note

package/6.bridge/3.bridge-composition-api.md

@@ -35,9 +35,9 @@ Because some composables have been removed and don't yet have a replacement, thi
 
 You don't have to immediately update your imports yet - Nuxt Bridge will automatically provide a 'shim' for most imports you currently have, to give you time to migrate to the new, Nuxt 3-compatible composables, with the following exceptions:
 
-- `withContext` has been removed. See [below](/docs/4.x/bridge/nuxt3-compatible-api#usecontext-and-withcontext).
+- `withContext` has been removed. See [below](/docs/bridge/nuxt3-compatible-api#usecontext-and-withcontext).
 - `useStatic` has been removed. There is no current replacement. Feel free to raise a discussion if you have a use case for this.
-- `reqRef` and `reqSsrRef`, which were deprecated, have now been removed entirely. Follow the instructions below regarding [ssrRef](/docs/4.x/bridge/nuxt3-compatible-api#ssrref-and-shallowssrref) to replace this.
+- `reqRef` and `reqSsrRef`, which were deprecated, have now been removed entirely. Follow the instructions below regarding [ssrRef](/docs/bridge/nuxt3-compatible-api#ssrref-and-shallowssrref) to replace this.
 
 ### Set `bridge.capi`
 
@@ -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](/docs/4.x/bridge/bridge-composition-api#definenuxtmiddleware)).
+You may also keep using Nuxt 2-style plugins, by removing the function (as with [defineNuxtMiddleware](/docs/bridge/bridge-composition-api#definenuxtmiddleware)).
 
 Remove the `defineNuxtPlugin` wrapper:
 
@@ -113,13 +113,13 @@ 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/4.x/directory-structure/app/plugins#creating-plugins"}
+:ReadMore{link="/docs/directory-structure/app/plugins#creating-plugins"}
 
 ### `useRouter` and `useRoute`
 
-Nuxt Bridge provides direct replacements for these composables via [`useRouter`](/docs/4.x/api/composables/use-router)  and `useRoute`.
+Nuxt Bridge provides direct replacements for these composables via [`useRouter`](/docs/api/composables/use-router)  and `useRoute`.
 
-The only key difference is that [`useRoute`](/docs/4.x/api/composables/use-route) no longer returns a computed property.
+The only key difference is that [`useRoute`](/docs/api/composables/use-route) no longer returns a computed property.
 
 ```diff
 - import { useRouter, useRoute } from '@nuxtjs/composition-api'

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

@@ -7,7 +7,7 @@ description: 'Learn how to migrate from Nuxt 2 to Nuxt Bridge new plugins and mi
 
 You can now migrate to the Nuxt 3 plugins API, which is slightly different in format from Nuxt 2.
 
-Plugins now take only one argument (`nuxtApp`). You can find out more in [the docs](/docs/4.x/directory-structure/app/plugins).
+Plugins now take only one argument (`nuxtApp`). You can find out more in [the docs](/docs/directory-structure/app/plugins).
 
 ```ts [app/plugins/hello.ts]
 export default defineNuxtPlugin((nuxtApp) => {
@@ -17,7 +17,7 @@ export default defineNuxtPlugin((nuxtApp) => {
 ```
 
 ::note
-If you want to use the new Nuxt composables (such as [`useNuxtApp`](/docs/4.x/api/composables/use-nuxt-app) or `useRuntimeConfig`) within your plugins, you will need to use the `defineNuxtPlugin` helper for those plugins.
+If you want to use the new Nuxt composables (such as [`useNuxtApp`](/docs/api/composables/use-nuxt-app) or `useRuntimeConfig`) within your plugins, you will need to use the `defineNuxtPlugin` helper for those plugins.
 ::
 
 ::warning
@@ -28,7 +28,7 @@ Although a compatibility interface is provided via `nuxtApp.vueApp` you should a
 
 You can now migrate to the Nuxt 3 middleware API, which is slightly different in format from Nuxt 2.
 
-Middleware now take only two argument (`to`, `from`). You can find out more in [the docs](/docs/4.x/directory-structure/app/middleware).
+Middleware now take only two argument (`to`, `from`). You can find out more in [the docs](/docs/directory-structure/app/middleware).
 
 ```ts twoslash
 export default defineNuxtRouteMiddleware((to) => {
@@ -44,7 +44,7 @@ Use of `defineNuxtRouteMiddleware` is not supported outside of the `app/middlewa
 
 ## definePageMeta
 
-You can also use [`definePageMeta`](/docs/4.x/api/utils/define-page-meta) in Nuxt Bridge.
+You can also use [`definePageMeta`](/docs/api/utils/define-page-meta) in Nuxt Bridge.
 
 It can be enabled with the `macros.pageMeta` option in your configuration file