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

package/6.bridge/5.nuxt3-compatible-api.md

@@ -9,7 +9,7 @@ By migrating from `@nuxtjs/composition-api` to the Nuxt 3 compatible API, there
 
 These two functions have been replaced with a new composable that works very similarly under the hood: `useState`.
 
-The key differences are that you must provide a _key_ for this state (which Nuxt generated automatically for `ssrRef` and `shallowSsrRef`), and that it can only be called within a Nuxt 3 plugin (which is defined by `defineNuxtPlugin`) or a component instance. (In other words, you cannot use [`useState`](/docs/4.x/api/composables/use-state) with a global/ambient context, because of the danger of shared state across requests.)
+The key differences are that you must provide a _key_ for this state (which Nuxt generated automatically for `ssrRef` and `shallowSsrRef`), and that it can only be called within a Nuxt 3 plugin (which is defined by `defineNuxtPlugin`) or a component instance. (In other words, you cannot use [`useState`](/docs/api/composables/use-state) with a global/ambient context, because of the danger of shared state across requests.)
 
 ```diff
 - import { ssrRef } from '@nuxtjs/composition-api'
@@ -24,7 +24,7 @@ The key differences are that you must provide a _key_ for this state (which Nuxt
 
 Because the state is keyed, you can access the same state from multiple locations, as long as you are using the same key.
 
-You can read more about how to use this composable in [the Nuxt 3 docs](/docs/4.x/api/composables/use-state).
+You can read more about how to use this composable in [the Nuxt 3 docs](/docs/api/composables/use-state).
 
 ## `ssrPromise`
 
@@ -32,7 +32,7 @@ This function has been removed, and you will need to find an alternative impleme
 
 ## `onGlobalSetup`
 
-This function has been removed, but its use cases can be met by using [`useNuxtApp`](/docs/4.x/api/composables/use-nuxt-app) or [`useState`](/docs/4.x/api/composables/use-state) within `defineNuxtPlugin`. You can also run any custom code within the `setup()` function of a layout.
+This function has been removed, but its use cases can be met by using [`useNuxtApp`](/docs/api/composables/use-nuxt-app) or [`useState`](/docs/api/composables/use-state) within `defineNuxtPlugin`. You can also run any custom code within the `setup()` function of a layout.
 
 ```diff
 - import { onGlobalSetup } from '@nuxtjs/composition-api'
@@ -84,14 +84,14 @@ const wrapProperty = (property: string, makeComputed = true) => () => {
 
 ## `useAsync` and `useFetch`
 
-These two composables can be replaced with `useLazyAsyncData` and `useLazyFetch`, which are documented [in the Nuxt 3 docs](/docs/4.x/getting-started/data-fetching). Just like the previous `@nuxtjs/composition-api` composables, these composables do not block route navigation on the client-side (hence the 'lazy' part of the name).
+These two composables can be replaced with `useLazyAsyncData` and `useLazyFetch`, which are documented [in the Nuxt 3 docs](/docs/getting-started/data-fetching). Just like the previous `@nuxtjs/composition-api` composables, these composables do not block route navigation on the client-side (hence the 'lazy' part of the name).
 
 ::important
 Note that the API is entirely different, despite similar sounding names. Importantly, you should not attempt to change the value of other variables outside the composable (as you may have been doing with the previous `useFetch`).
 ::
 
 ::warning
-The `useLazyFetch` must have been configured for [Nitro](/docs/4.x/bridge/nitro).
+The `useLazyFetch` must have been configured for [Nitro](/docs/bridge/nitro).
 ::
 
 Migrating to the new composables from `useAsync`:
@@ -152,7 +152,7 @@ title.value = 'new title'
 Be careful not to use both `useNuxt2Meta()` and the Options API `head()` within the same component, as behavior may be unpredictable.
 ::
 
-Nuxt Bridge also provides a Nuxt 3-compatible meta implementation that can be accessed with the [`useHead`](/docs/4.x/api/composables/use-head) composable.
+Nuxt Bridge also provides a Nuxt 3-compatible meta implementation that can be accessed with the [`useHead`](/docs/api/composables/use-head) composable.
 
 ```diff
 <script setup>
@@ -175,9 +175,9 @@ export default defineNuxtConfig({
 })
 ```
 
-This [`useHead`](/docs/4.x/api/composables/use-head) composable uses `@unhead/vue` under the hood (rather than `vue-meta`) to manipulate your `<head>`. Accordingly, it is recommended not to use both the native Nuxt 2 `head()` properties as well as [`useHead`](/docs/4.x/api/composables/use-head) , as they may conflict.
+This [`useHead`](/docs/api/composables/use-head) composable uses `@unhead/vue` under the hood (rather than `vue-meta`) to manipulate your `<head>`. Accordingly, it is recommended not to use both the native Nuxt 2 `head()` properties as well as [`useHead`](/docs/api/composables/use-head) , as they may conflict.
 
-For more information on how to use this composable, see [the Nuxt 3 docs](/docs/4.x/getting-started/seo-meta).
+For more information on how to use this composable, see [the Nuxt 3 docs](/docs/getting-started/seo-meta).
 
 ### Explicit Imports
 
@@ -204,4 +204,4 @@ export default defineNuxtConfig({
 })
 ```
 
-This will disable auto-imports completely but it's still possible to use [explicit imports](/docs/4.x/bridge/nuxt3-compatible-api#explicit-imports) from `#imports`.
+This will disable auto-imports completely but it's still possible to use [explicit imports](/docs/bridge/nuxt3-compatible-api#explicit-imports) from `#imports`.

package/6.bridge/6.meta.md

@@ -3,7 +3,7 @@ title: Meta Tags
 description: 'Learn how to migrate from Nuxt 2 to Nuxt Bridge new meta tags.'
 ---
 
-If you need to access the component state with `head`, you should migrate to using [`useHead`](/docs/4.x/api/composables/use-head) .
+If you need to access the component state with `head`, you should migrate to using [`useHead`](/docs/api/composables/use-head) .
 
 If you need to use the Options API, there is a `head()` method you can use when you use `defineNuxtComponent`.
 
@@ -60,7 +60,7 @@ export default defineNuxtConfig({
 
 ## `useHead` Composables
 
-Nuxt Bridge provides a new Nuxt 3 meta API that can be accessed with a new [`useHead`](/docs/4.x/api/composables/use-head) composable.
+Nuxt Bridge provides a new Nuxt 3 meta API that can be accessed with a new [`useHead`](/docs/api/composables/use-head) composable.
 
 ```vue
 <script setup lang="ts">
@@ -71,14 +71,14 @@ useHead({
 ```
 
 ::tip
-This [`useHead`](/docs/4.x/api/composables/use-head) composable uses `@unhead/vue` under the hood (rather than `vue-meta`) to manipulate your `<head>`.
+This [`useHead`](/docs/api/composables/use-head) composable uses `@unhead/vue` under the hood (rather than `vue-meta`) to manipulate your `<head>`.
 ::
 
 ::warning
-We recommend not using the native Nuxt 2 `head()` properties in addition to [`useHead`](/docs/4.x/api/composables/use-head) , as they may conflict.
+We recommend not using the native Nuxt 2 `head()` properties in addition to [`useHead`](/docs/api/composables/use-head) , as they may conflict.
 ::
 
-For more information on how to use this composable, see [the docs](/docs/4.x/getting-started/seo-meta).
+For more information on how to use this composable, see [the docs](/docs/getting-started/seo-meta).
 
 ## Options API
 

package/6.bridge/7.runtime-config.md

@@ -4,7 +4,7 @@ description: 'Nuxt provides a runtime config API to expose configuration and sec
 ---
 
 ::warning
-When using `runtimeConfig` option, [nitro](/docs/4.x/bridge/nitro) must have been configured.
+When using `runtimeConfig` option, [nitro](/docs/bridge/nitro) must have been configured.
 ::
 
 ## Update Runtime Config

package/6.bridge/8.nitro.md

@@ -53,7 +53,7 @@ deno add -D npm:nuxi
 
 ### Nuxi
 
-Nuxt 3 introduced the new Nuxt CLI command [`nuxi`](/docs/4.x/api/commands/add). Update your scripts as follows to leverage the better support from Nuxt Bridge:
+Nuxt 3 introduced the new Nuxt CLI command [`nuxi`](/docs/api/commands/add). Update your scripts as follows to leverage the better support from Nuxt Bridge:
 
 ```diff
 {

package/6.bridge/9.vite.md

@@ -4,7 +4,7 @@ description: 'Activate Vite to your Nuxt 2 application with Nuxt Bridge.'
 ---
 
 ::warning
-When using `vite`, [nitro](/docs/4.x/bridge/nitro) must have been configured.
+When using `vite`, [nitro](/docs/bridge/nitro) must have been configured.
 ::
 
 ## Remove Modules

package/7.migration/1.overview.md

@@ -16,9 +16,9 @@ Some of these significant changes include:
 1. Moving from a runtime Nuxt dependency to a minimal, standalone server compiled with nitropack.
 
 ::tip
-If you need to remain on Nuxt 2, but want to benefit from Nuxt 3 features in Nuxt 2, you can alternatively check out [how to get started with Bridge](/docs/4.x/bridge/overview).
+If you need to remain on Nuxt 2, but want to benefit from Nuxt 3 features in Nuxt 2, you can alternatively check out [how to get started with Bridge](/docs/bridge/overview).
 ::
 
 ## Next Steps
 
-- Learn about differences in [configuration](/docs/4.x/migration/configuration)
+- Learn about differences in [configuration](/docs/migration/configuration)

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/4.x/guide/concepts/typescript"}
+:read-more{to="/docs/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/4.x/guide/concepts/server-engine"}
+:read-more{to="/docs/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/4.x/directory-structure/server"}
-:read-more{to="/docs/4.x/guide/going-further/hooks#server-hooks-runtime"}
+:read-more{to="/docs/directory-structure/server"}
+:read-more{to="/docs/guide/going-further/hooks#server-hooks-runtime"}

package/7.migration/2.configuration.md

@@ -100,7 +100,7 @@ Nuxt configuration will be loaded using [`unjs/jiti`](https://github.com/unjs/ji
 
 #### ESM Syntax
 
-Nuxt 3 is an [ESM native framework](/docs/4.x/guide/concepts/esm). Although [`unjs/jiti`](https://github.com/unjs/jiti) provides semi compatibility when loading `nuxt.config` file, avoid any usage of `require` and `module.exports` in this file.
+Nuxt 3 is an [ESM native framework](/docs/guide/concepts/esm). Although [`unjs/jiti`](https://github.com/unjs/jiti) provides semi compatibility when loading `nuxt.config` file, avoid any usage of `require` and `module.exports` in this file.
 
 1. Change `module.exports` to `export default`
 1. Change `const lib = require('lib')` to `import lib from 'lib'`
@@ -133,20 +133,20 @@ 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/modules).
+If you are a module author, you can check out [more information about module compatibility](/docs/migration/module-authors) and [our module author guide](/docs/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/4.x/directory-structure/public"}
+:read-more{to="/docs/directory-structure/public"}
 
 ## TypeScript
 
 It will be much easier to migrate your application if you use Nuxt's TypeScript integration. This does not mean you need to write your application in TypeScript, just that Nuxt will provide automatic type hints for your editor.
 
-You can read more about Nuxt's TypeScript support [in the docs](/docs/4.x/guide/concepts/typescript).
+You can read more about Nuxt's TypeScript support [in the docs](/docs/guide/concepts/typescript).
 
 ::note
 Nuxt can type-check your app using [`vue-tsc`](https://github.com/vuejs/language-tools/tree/master/packages/tsc) with `nuxt typecheck` command.
@@ -177,7 +177,7 @@ Nuxt can type-check your app using [`vue-tsc`](https://github.com/vuejs/language
    ```
 
 1. Run `npx nuxt prepare` to generate the tsconfig files.
-1. Install Volar following the instructions in the [docs](/docs/4.x/getting-started/installation#prerequisites).
+1. Install Volar following the instructions in the [docs](/docs/getting-started/installation#prerequisites).
 
 ## Vue Changes
 
@@ -227,7 +227,7 @@ export const useMainStore = defineStore('main', {
 })
 ```
 
-Create a [plugin](/docs/4.x/directory-structure/app/plugins) file to globalize your store:
+Create a [plugin](/docs/directory-structure/app/plugins) file to globalize your store:
 
 ```ts [app/plugins/pinia.ts]
 import { useMainStore } from '~/store'

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/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/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/4.x/directory-structure/app/plugins"}
+:read-more{to="/docs/directory-structure/app/plugins"}
 
 ### Vue Compatibility
 
@@ -33,11 +33,11 @@ When Nuxt 3 users add your module, you will not have access to the module contai
 
 Migrating to `@nuxt/bridge` is the first and most important step for supporting Nuxt 3.
 
-If you have a fixture or example in your module, add `@nuxt/bridge` package to its config (see [example](/docs/4.x/bridge/overview#update-nuxtconfig))
+If you have a fixture or example in your module, add `@nuxt/bridge` package to its config (see [example](/docs/bridge/overview#update-nuxtconfig))
 
 ### 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.
 
 ### Ensure Plugins Default Export
 
@@ -69,16 +69,16 @@ export default () => { }
 
 With Nuxt 3, Nuxt is now a build-time-only dependency, which means that modules shouldn't attempt to hook into the Nuxt runtime.
 
-Your module should work even if it's only added to [`buildModules`](/docs/4.x/api/nuxt-config#runtimeconfig) (instead of `modules`). For example:
+Your module should work even if it's only added to [`buildModules`](/docs/api/nuxt-config#runtimeconfig) (instead of `modules`). For example:
 
-- Avoid updating `process.env` within a Nuxt module and reading by a Nuxt plugin; use [`runtimeConfig`](/docs/4.x/api/nuxt-config#runtimeconfig) instead.
+- Avoid updating `process.env` within a Nuxt module and reading by a Nuxt plugin; use [`runtimeConfig`](/docs/api/nuxt-config#runtimeconfig) instead.
 - (*) Avoid depending on runtime hooks like `vue-renderer:*` for production
 - (*) Avoid adding `serverMiddleware` by importing them inside the module. Instead, add them by referencing a file path so that they are independent of the module's context
 
 (*) 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/modules).
+Continue reading about Nuxt 3 modules in the [Modules Author Guide](/docs/guide/modules).
 ::
 
 ### Use TypeScript (Optional)

package/7.migration/3.auto-imports.md

@@ -4,14 +4,14 @@ description:  Nuxt 3 adopts a minimal friction approach, meaning wherever possib
 ---
 
 ::note
-In the rest of the migration documentation, you will notice that key Nuxt and Vue utilities do not have explicit imports. This is not a typo; Nuxt will automatically import them for you, and you should get full type hinting if you have followed [the instructions](/docs/4.x/migration/configuration#typescript) to use Nuxt's TypeScript support.
+In the rest of the migration documentation, you will notice that key Nuxt and Vue utilities do not have explicit imports. This is not a typo; Nuxt will automatically import them for you, and you should get full type hinting if you have followed [the instructions](/docs/migration/configuration#typescript) to use Nuxt's TypeScript support.
 ::
 
-[Read more about auto imports](/docs/4.x/guide/concepts/auto-imports)
+[Read more about auto imports](/docs/guide/concepts/auto-imports)
 
 ## Migration
 
-1. If you have been using `@nuxt/components` in Nuxt 2, you can remove `components: true` in your `nuxt.config`. If you had a more complex setup, then note that the component options have changed somewhat. See the [components documentation](/docs/4.x/directory-structure/app/components) for more information.
+1. If you have been using `@nuxt/components` in Nuxt 2, you can remove `components: true` in your `nuxt.config`. If you had a more complex setup, then note that the component options have changed somewhat. See the [components documentation](/docs/directory-structure/app/components) for more information.
 
 ::tip
 You can look at `.nuxt/types/components.d.ts` and `.nuxt/types/imports.d.ts` to see how Nuxt has resolved your components and composable auto-imports.

package/7.migration/4.meta.md

@@ -5,8 +5,8 @@ description: Manage your meta tags, from Nuxt 2 to Nuxt 3.
 
 Nuxt 3 provides several different ways to manage your meta tags:
 1. Through your `nuxt.config`.
-2. Through the [`useHead`](/docs/4.x/api/composables/use-head) [composable](/docs/4.x/getting-started/seo-meta)
-3. Through [global meta components](/docs/4.x/getting-started/seo-meta)
+2. Through the [`useHead`](/docs/api/composables/use-head) [composable](/docs/getting-started/seo-meta)
+3. Through [global meta components](/docs/getting-started/seo-meta)
 
 You can customize `title`, `titleTemplate`, `base`, `script`, `noscript`, `style`, `meta`, `link`, `htmlAttrs` and `bodyAttrs`.
 
@@ -14,12 +14,12 @@ 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/4.x/getting-started/seo-meta"}
+:read-more{to="/docs/getting-started/seo-meta"}
 
 ## Migration
 
 1. In your `nuxt.config`, rename `head` to `meta`. Consider moving this shared meta configuration into your `app.vue` instead. (Note that objects no longer have a `hid` key for deduplication.)
-2. If you need to access the component state with `head`, you should migrate to using [`useHead`](/docs/4.x/api/composables/use-head) . You might also consider using the built-in meta-components.
+2. If you need to access the component state with `head`, you should migrate to using [`useHead`](/docs/api/composables/use-head) . You might also consider using the built-in meta-components.
 3. If you need to use the Options API, there is a `head()` method you can use when you use `defineNuxtComponent`.
 
 ### useHead

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

@@ -31,9 +31,9 @@ export default defineNuxtPlugin((nuxtApp) => {
 
 ::
 
-:read-more{to="/docs/4.x/directory-structure/app/plugins"}
+:read-more{to="/docs/directory-structure/app/plugins"}
 
-::read-more{to="/docs/4.x/api/composables/use-nuxt-app"}
+::read-more{to="/docs/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/4.x/directory-structure/app/middleware"}
+:read-more{to="/docs/directory-structure/app/middleware"}
 
 ### Migration
 

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

@@ -13,19 +13,19 @@ 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/4.x/directory-structure/app/app"}
+:read-more{to="/docs/directory-structure/app/app"}
 
-:link-example{to="/docs/4.x/examples/hello-world"}
+:link-example{to="/docs/examples/hello-world"}
 
 ### Migration
 
-Consider creating an `app.vue` file and including any logic that needs to run once at the top-level of your app. You can check out [an example here](/docs/4.x/directory-structure/app/app).
+Consider creating an `app.vue` file and including any logic that needs to run once at the top-level of your app. You can check out [an example here](/docs/directory-structure/app/app).
 
 ## Layouts
 
 If you are using layouts in your app for multiple pages, there is only a slight change required.
 
-In Nuxt 2, the `<Nuxt>` component is used within a layout to render the current page. In Nuxt 3, layouts use slots instead, so you will have to replace that component with a `<slot />`. This also allows advanced use cases with named and scoped slots. [Read more about layouts](/docs/4.x/directory-structure/app/layouts).
+In Nuxt 2, the `<Nuxt>` component is used within a layout to render the current page. In Nuxt 3, layouts use slots instead, so you will have to replace that component with a `<slot />`. This also allows advanced use cases with named and scoped slots. [Read more about layouts](/docs/directory-structure/app/layouts).
 
 You will also need to change how you define the layout used by a page using the `definePageMeta` compiler macro. Layouts will be kebab-cased. So `app/layouts/customLayout.vue` becomes `custom-layout` when referenced in your page.
 
@@ -42,7 +42,7 @@ You will also need to change how you define the layout used by a page using the
         </div>
       </template>
     ```
-2. Use [`definePageMeta`](/docs/4.x/api/utils/define-page-meta) to select the layout used by your page.
+2. Use [`definePageMeta`](/docs/api/utils/define-page-meta) to select the layout used by your page.
     ```diff [app/pages/index.vue]
     + <script setup>
     + definePageMeta({
@@ -54,7 +54,7 @@ You will also need to change how you define the layout used by a page using the
     - }
       </script>
     ```
-3. Move `~/layouts/_error.vue` to `~/error.vue`. See [the error handling docs](/docs/4.x/getting-started/error-handling). If you want to ensure that this page uses a layout, you can use [`<NuxtLayout>`](/docs/4.x/directory-structure/app/layouts) directly within `error.vue`:
+3. Move `~/layouts/_error.vue` to `~/error.vue`. See [the error handling docs](/docs/getting-started/error-handling). If you want to ensure that this page uses a layout, you can use [`<NuxtLayout>`](/docs/directory-structure/app/layouts) directly within `error.vue`:
     ```vue [error.vue]
     <template>
       <div>
@@ -67,7 +67,7 @@ You will also need to change how you define the layout used by a page using the
 
 ## Pages
 
-Nuxt 3 ships with an optional `vue-router` integration triggered by the existence of a [`app/pages/`](/docs/4.x/directory-structure/app/pages) directory in your source directory. If you only have a single page, you may consider instead moving it to `app.vue` for a lighter build.
+Nuxt 3 ships with an optional `vue-router` integration triggered by the existence of a [`app/pages/`](/docs/directory-structure/app/pages) directory in your source directory. If you only have a single page, you may consider instead moving it to `app.vue` for a lighter build.
 
 ### Dynamic Routes
 
@@ -84,19 +84,19 @@ 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/4.x/directory-structure/app/pages#special-metadata"}
+:read-more{to="/docs/directory-structure/app/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/4.x/getting-started/transitions"}
+:read-more{to="/docs/getting-started/transitions"}
 
 ### Migration
 
 1. Rename any pages with dynamic parameters to match the new format.
 2. Update `<Nuxt>` and `<NuxtChild>` to be `<NuxtPage>`.
-3. If you're using the Composition API, you can also migrate `this.$route` and `this.$router` to use [`useRoute`](/docs/4.x/api/composables/use-route) and [`useRouter`](/docs/4.x/api/composables/use-router)  composables.
+3. If you're using the Composition API, you can also migrate `this.$route` and `this.$router` to use [`useRoute`](/docs/api/composables/use-route) and [`useRouter`](/docs/api/composables/use-router)  composables.
 
 #### Example: Dynamic Routes
 
@@ -186,18 +186,18 @@ definePageMeta({
 
 ## `<NuxtLink>` Component
 
-Most of the syntax and functionality are the same for the global [NuxtLink](/docs/4.x/api/components/nuxt-link) component. If you have been using the shortcut `<NLink>` format, you should update this to use `<NuxtLink>`.
+Most of the syntax and functionality are the same for the global [NuxtLink](/docs/api/components/nuxt-link) component. If you have been using the shortcut `<NLink>` format, you should update this to use `<NuxtLink>`.
 
 `<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/4.x/api/components/nuxt-link"}
+:read-more{to="/docs/api/components/nuxt-link"}
 
 ## Programmatic Navigation
 
 When migrating from Nuxt 2 to Nuxt 3, you will have to update how you programmatically navigate your users. In Nuxt 2, you had access to the underlying Vue Router with `this.$router`. In Nuxt 3, you can use the `navigateTo()` utility method which allows you to pass a route and parameters to Vue Router.
 
 ::warning
-Make sure to always `await` on [`navigateTo`](/docs/4.x/api/utils/navigate-to) or chain its result by returning from functions.
+Make sure to always `await` on [`navigateTo`](/docs/api/utils/navigate-to) or chain its result by returning from functions.
 ::
 
 ::code-group

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

@@ -5,7 +5,7 @@ description: 'Learn how to migrate from Nuxt 2 components options to Nuxt 3 comp
 
 ## `asyncData` and `fetch`
 
-Nuxt 3 provides new options for [fetching data from an API](/docs/4.x/getting-started/data-fetching).
+Nuxt 3 provides new options for [fetching data from an API](/docs/getting-started/data-fetching).
 
 <!-- TODO: Intro to <script setup> -->
 <!-- TODO: Mention about options compatibility with asyncData -->
@@ -14,17 +14,17 @@ Nuxt 3 provides new options for [fetching data from an API](/docs/4.x/getting-st
 
 In Nuxt 2 you might use `@nuxtjs/axios` or `@nuxt/http` to fetch your data - or just the polyfilled global `fetch`.
 
-In Nuxt 3 you can use a globally available `fetch` method that has the same API as [the Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch) or [`$fetch`](/docs/4.x/api/utils/dollarfetch) method which is using [unjs/ofetch](https://github.com/unjs/ofetch). It has a number of benefits, including:
+In Nuxt 3 you can use a globally available `fetch` method that has the same API as [the Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch) or [`$fetch`](/docs/api/utils/dollarfetch) method which is using [unjs/ofetch](https://github.com/unjs/ofetch). It has a number of benefits, including:
 
-1. It will handle 'smartly' making [direct API calls](/docs/4.x/guide/concepts/server-engine#direct-api-calls) if it's running on the server, or making a client-side call to your API if it's running on the client. (It can also handle calling third-party APIs.)
+1. It will handle 'smartly' making [direct API calls](/docs/guide/concepts/server-engine#direct-api-calls) if it's running on the server, or making a client-side call to your API if it's running on the client. (It can also handle calling third-party APIs.)
 
 2. Plus, it comes with convenience features including automatically parsing responses and stringifying data.
 
-You can read more [about direct API calls](/docs/4.x/guide/concepts/server-engine#direct-api-calls) or [fetching data](/docs/4.x/getting-started/data-fetching).
+You can read more [about direct API calls](/docs/guide/concepts/server-engine#direct-api-calls) or [fetching data](/docs/getting-started/data-fetching).
 
 ### Composables
 
-Nuxt 3 provides new composables for fetching data: [`useAsyncData`](/docs/4.x/api/composables/use-async-data) and `useFetch`. They each have 'lazy' variants (`useLazyAsyncData` and `useLazyFetch`), which do not block client-side navigation.
+Nuxt 3 provides new composables for fetching data: [`useAsyncData`](/docs/api/composables/use-async-data) and `useFetch`. They each have 'lazy' variants (`useLazyAsyncData` and `useLazyFetch`), which do not block client-side navigation.
 
 In Nuxt 2, you'd fetch your data in your component using a syntax similar to:
 
@@ -57,21 +57,21 @@ const { data: post, refresh } = await useFetch(`https://api.nuxtjs.dev/posts/${p
 You can now use `post` inside of your Nuxt 3 template, or call `refresh` to update the data.
 
 ::note
-Despite the names, [`useFetch`](/docs/4.x/api/composables/use-fetch) is not a direct replacement of the `fetch()` hook. Rather, [`useAsyncData`](/docs/4.x/api/composables/use-async-data) replaces both hooks and is more customizable; it can do more than simply fetching data from an endpoint. [`useFetch`](/docs/4.x/api/composables/use-fetch) is a convenience wrapper around [`useAsyncData`](/docs/4.x/api/composables/use-async-data) for simply fetching data from an endpoint.
+Despite the names, [`useFetch`](/docs/api/composables/use-fetch) is not a direct replacement of the `fetch()` hook. Rather, [`useAsyncData`](/docs/api/composables/use-async-data) replaces both hooks and is more customizable; it can do more than simply fetching data from an endpoint. [`useFetch`](/docs/api/composables/use-fetch) is a convenience wrapper around [`useAsyncData`](/docs/api/composables/use-async-data) for simply fetching data from an endpoint.
 ::
 
 ### Migration
 
-1. Replace the `asyncData` hook with [`useAsyncData`](/docs/4.x/api/composables/use-async-data) or [`useFetch`](/docs/4.x/api/composables/use-fetch) in your page/component.
-2. Replace the `fetch` hook with [`useAsyncData`](/docs/4.x/api/composables/use-async-data) or [`useFetch`](/docs/4.x/api/composables/use-fetch) in your component.
+1. Replace the `asyncData` hook with [`useAsyncData`](/docs/api/composables/use-async-data) or [`useFetch`](/docs/api/composables/use-fetch) in your page/component.
+2. Replace the `fetch` hook with [`useAsyncData`](/docs/api/composables/use-async-data) or [`useFetch`](/docs/api/composables/use-fetch) in your component.
 
 ## `head`
 
-:read-more{to="/docs/4.x/migration/meta"}
+:read-more{to="/docs/migration/meta"}
 
 ## `key`
 
-You can now define a key within the [`definePageMeta`](/docs/4.x/api/utils/define-page-meta) compiler macro.
+You can now define a key within the [`definePageMeta`](/docs/api/utils/define-page-meta) compiler macro.
 
 ```diff [app/pages/index.vue]
 - <script>
@@ -91,7 +91,7 @@ You can now define a key within the [`definePageMeta`](/docs/4.x/api/utils/defin
 
 ## `layout`
 
-:read-more{to="/docs/4.x/migration/pages-and-layouts"}
+:read-more{to="/docs/migration/pages-and-layouts"}
 
 ## `loading`
 
@@ -99,12 +99,12 @@ This feature is not yet supported in Nuxt 3.
 
 ## `middleware`
 
-:read-more{to="/docs/4.x/migration/plugins-and-middleware"}
+:read-more{to="/docs/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 an `~/router.options.ts` (see [docs](/docs/4.x/guide/recipes/custom-routing#router-options)) for more info.
-Similar to `key`, specify it within the [`definePageMeta`](/docs/4.x/api/utils/define-page-meta) compiler macro.
+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 `~/router.options.ts` (see [docs](/docs/guide/recipes/custom-routing#router-options)) for more info.
+Similar to `key`, specify it within the [`definePageMeta`](/docs/api/utils/define-page-meta) compiler macro.
 
 ```diff [app/pages/index.vue]
 - <script>
@@ -120,7 +120,7 @@ Similar to `key`, specify it within the [`definePageMeta`](/docs/4.x/api/utils/d
 
 ## `transition`
 
-:read-more{to="/docs/4.x/getting-started/transitions"}
+:read-more{to="/docs/getting-started/transitions"}
 
 ## `validate`
 

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

@@ -5,16 +5,16 @@ description: 'Learn how to migrate from Nuxt 2 to Nuxt 3 runtime config.'
 
 If you wish to reference environment variables within your Nuxt 3 app, you will need to use runtime config.
 
-When referencing these variables within your components, you will have to use the [`useRuntimeConfig`](/docs/4.x/api/composables/use-runtime-config) composable in your setup method (or Nuxt plugin).
+When referencing these variables within your components, you will have to use the [`useRuntimeConfig`](/docs/api/composables/use-runtime-config) composable in your setup method (or Nuxt plugin).
 
-In the `server/` portion of your app, you can use [`useRuntimeConfig`](/docs/4.x/api/composables/use-runtime-config) without any import.
+In the `server/` portion of your app, you can use [`useRuntimeConfig`](/docs/api/composables/use-runtime-config) without any import.
 
-:read-more{to="/docs/4.x/guide/going-further/runtime-config"}
+:read-more{to="/docs/guide/going-further/runtime-config"}
 
 ## Migration
 
 1. Add any environment variables that you use in your app to the `runtimeConfig` property of the `nuxt.config` file.
-2. Migrate `process.env` to [`useRuntimeConfig`](/docs/4.x/api/composables/use-runtime-config) throughout the Vue part of your app.
+2. Migrate `process.env` to [`useRuntimeConfig`](/docs/api/composables/use-runtime-config) throughout the Vue part of your app.
 
 ::code-group
 

package/README.md

@@ -4,7 +4,7 @@ navigation: false
 
 # Nuxt Docs
 
-This repository contains the documentation of Nuxt, hosted on <https://nuxt.com/docs/4.x/getting-started/introduction>
+This repository contains the documentation of Nuxt, hosted on <https://nuxt.com/docs>
 
 ## Contributing
 

package/errors/e8007.md

@@ -0,0 +1,28 @@
+---
+title: 'NUXT_E8007'
+description: 'A route relies on client-side JavaScript but noScripts will strip scripts in production.'
+navigation: false
+---
+
+# E8007
+
+With `features.noScripts: 'production'` (the default when `noScripts` is enabled), scripts are only stripped from rendered HTML in production builds. In development the page still ships JavaScript, so behaviour that depends on it (lazy hydration strategies, `nuxt-client` components inside server components) appears to work in dev and then silently breaks after deployment.
+
+This warning is emitted during development when a rendered route uses one of these features.
+
+## Resolution
+
+Either remove the client-side dependency from the affected route, or scope script stripping to the routes that are genuinely static using the `noScripts` route rule (which applies in development too, so any breakage is visible immediately):
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  routeRules: {
+    '/static/**': { noScripts: true },
+  },
+})
+```
+
+Alternatively, set `features.noScripts: 'all'` to strip scripts in development as well, making the production behaviour observable in dev.
+
+::read-more{to="/docs/guide/going-further/features#noscripts"}
+::

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.5.1-29752449.30d24817",
+  "version": "4.5.2-2610052030-052d82e",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",
@@ -17,5 +17,5 @@
     "**/*.md",
     "**/*.yml"
   ],
-  "_name": "@nuxt/docs"
+  "scripts": {}
 }

package/4.api/4.commands/.navigation.yml

@@ -1,3 +0,0 @@
-title: 'Commands'
-titleTemplate: '%s · Nuxt Commands'
-icon: i-lucide-square-terminal