@nuxt/docs-nightly 4.1.3-29313364.98ecc620 → 4.1.3-29314777.50febbbb

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

@@ -310,7 +310,7 @@ This can be overridden with `definePageMeta` on an individual page.
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt View Transition API docs](https://nuxt.com/docs/getting-started/transitions#view-transitions-api-experimental)
+**See**: [Nuxt View Transition API docs](https://nuxt.com/docs/4.x/getting-started/transitions#view-transitions-api-experimental)
 
 ## appConfig
 
@@ -442,7 +442,7 @@ Any components in the directories configured here can be used throughout your pa
 }
 ```
 
-**See**: [`app/components/` directory documentation](https://nuxt.com/docs/guide/directory-structure/app/components)
+**See**: [`app/components/` directory documentation](https://nuxt.com/docs/4.x/guide/directory-structure/app/components)
 
 ## css
 
@@ -1380,7 +1380,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](https://nuxt.com/docs/guide/directory-structure/app/composables)
+**See**: [Nuxt documentation](https://nuxt.com/docs/4.x/guide/directory-structure/app/composables)
 
 ### `dirs`
 
@@ -1676,7 +1676,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](https://nuxt.com/docs/guide/directory-structure/plugins)
+**See**: [`app/plugins/` directory documentation](https://nuxt.com/docs/4.x/guide/directory-structure/plugins)
 
 **Example**:
 ```js
@@ -1818,7 +1818,7 @@ Each handler accepts the following options:
 
 - **Type**: `array`
 
-**See**: [`server/` directory documentation](https://nuxt.com/docs/guide/directory-structure/server)
+**See**: [`server/` directory documentation](https://nuxt.com/docs/4.x/guide/directory-structure/server)
 
 ::callout
 **Note**: Files from `server/api`, `server/middleware` and `server/routes` will be automatically registered by Nuxt.
@@ -2044,7 +2044,7 @@ If set to true, this will type check in development. You can restrict this to bu
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt TypeScript docs](https://nuxt.com/docs/guide/concepts/typescript)
+**See**: [Nuxt TypeScript docs](https://nuxt.com/docs/4.x/guide/concepts/typescript)
 
 ## unhead
 

package/3.api/index.md

@@ -7,25 +7,25 @@ surround: false
 ---
 
 ::card-group
-  ::card{icon="i-lucide-box" title="Components" to="/docs/api/components/client-only"}
+  ::card{icon="i-lucide-box" title="Components" to="/docs/4.x/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/api/composables/use-app-config"}
+  ::card{icon="i-lucide-arrow-left-right" title="Composables" to="/docs/4.x/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/api/utils/dollarfetch"}
+  ::card{icon="i-lucide-square-function" title="Utils" to="/docs/4.x/api/utils/dollarfetch"}
   Learn about Nuxt utility functions for navigation, error handling and more.
   ::
-  ::card{icon="i-lucide-square-terminal" title="Commands" to="/docs/api/commands/add"}
+  ::card{icon="i-lucide-square-terminal" title="Commands" to="/docs/4.x/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/api/kit/modules"}
+  ::card{icon="i-lucide-package" title="Nuxt Kit" to="/docs/4.x/api/kit/modules"}
   Understand Nuxt Kit utilities to create modules and control Nuxt.
   ::
-  ::card{icon="i-lucide-brain" title="Advanced" to="/docs/api/advanced/hooks"}
+  ::card{icon="i-lucide-brain" title="Advanced" to="/docs/4.x/api/advanced/hooks"}
   Go deep in Nuxt internals with Nuxt lifecycle hooks.
   ::
-  ::card{icon="i-lucide-cog" title="Nuxt Configuration" to="/docs/api/nuxt-config"}
+  ::card{icon="i-lucide-cog" title="Nuxt Configuration" to="/docs/4.x/api/nuxt-config"}
   Explore all Nuxt configuration options to customize your application.
   ::
 ::

package/5.community/4.contribution.md

@@ -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/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.
+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.
 
 #### 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/community/contribution#commit-conventions).
+When sending a pull request, make sure your PR's title also follows the [Commit Convention](/docs/4.x/community/contribution#commit-conventions).
 
 If your PR fixes or resolves existing issues, please make sure you mention them in the PR description.
 
@@ -106,7 +106,7 @@ If you need help while building it, feel free to [check in with us](/docs/4.x/co
 
 ### Make an RFC
 
-We highly recommend [creating a module](/docs/community/contribution#create-a-module) first to test out big new features and gain community adoption.
+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.
 
 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.
 
@@ -172,7 +172,7 @@ We recommend using [VS Code](https://code.visualstudio.com) along with the [ESLi
 
 #### No Prettier
 
-Since ESLint is already configured to format the code, there is no need to duplicate the functionality with Prettier. To format the code, you can run `yarn lint --fix`, `pnpm lint --fix`, or `bun run lint --fix` or referring the [ESLint section](/docs/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`, or `bun run lint --fix` or referring the [ESLint section](/docs/4.x/community/contribution#use-eslint) for IDE Setup.
 
 If you have Prettier installed in your editor, we recommend you disable it when working on the project to avoid conflict.
 
@@ -218,6 +218,6 @@ Here are some tips that may help improve your documentation:
   Nuxt will throw an error.
   ::
 
-::read-more{to="/docs/community/framework-contribution#documentation-guide"}
+::read-more{to="/docs/4.x/community/framework-contribution#documentation-guide"}
 Learn how to contribute to the documentation.
 ::

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

@@ -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/community/framework-contribution#playground) and [test](/docs/community/framework-contribution#testing) your changes before submitting a pull request.
+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.
 
 ### Playground
 

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](/docs/bridge/bridge-composition-api#definenuxtmiddleware)).
+You may also keep using Nuxt 2-style plugins, by removing the function (as with [defineNuxtMiddleware](/docs/4.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/app/plugins#creating-plugins"}
+:ReadMore{link="/docs/4.x/guide/directory-structure/app/plugins#creating-plugins"}
 
 ### `useRouter` and `useRoute`
 

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

@@ -201,4 +201,4 @@ export default defineNuxtConfig({
 })
 ```
 
-This will disable auto-imports completely but it's still possible to use [explicit imports](/docs/bridge/nuxt3-compatible-api#explicit-imports) from `#imports`.
+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`.

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

package/7.migration/2.configuration.md

@@ -138,7 +138,7 @@ If you are a module author, you can check out [more information about module com
 
 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/4.x/guide/directory-structure/public"}
 
 ## TypeScript
 

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

@@ -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/4.x/guide/directory-structure/plugins"}
 
 ### Vue Compatibility
 

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/4.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/4.x/guide/directory-structure/plugins"}
 
-::read-more{to="/docs/api/composables/use-nuxt-app"}
+::read-more{to="/docs/4.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/app/middleware"}
+:read-more{to="/docs/4.x/guide/directory-structure/app/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/4.x/guide/directory-structure/app"}
 
-:link-example{to="/docs/examples/hello-world"}
+:link-example{to="/docs/4.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/app/pages#special-metadata"}
+:read-more{to="/docs/4.x/guide/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/getting-started/transitions"}
+:read-more{to="/docs/4.x/getting-started/transitions"}
 
 ### Migration
 
@@ -186,7 +186,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/4.x/api/components/nuxt-link"}
 
 ## Programmatic Navigation
 

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

@@ -67,7 +67,7 @@ Despite the names, [`useFetch`](/docs/4.x/api/composables/use-fetch) is not a di
 
 ## `head`
 
-:read-more{to="/docs/migration/meta"}
+:read-more{to="/docs/4.x/migration/meta"}
 
 ## `key`
 
@@ -91,7 +91,7 @@ You can now define a key within the [`definePageMeta`](/docs/4.x/api/utils/defin
 
 ## `layout`
 
-:read-more{to="/docs/migration/pages-and-layouts"}
+:read-more{to="/docs/4.x/migration/pages-and-layouts"}
 
 ## `loading`
 
@@ -99,7 +99,7 @@ This feature is not yet supported in Nuxt 3.
 
 ## `middleware`
 
-:read-more{to="/docs/migration/plugins-and-middleware"}
+:read-more{to="/docs/4.x/migration/plugins-and-middleware"}
 
 ## `scrollToTop`
 
@@ -120,7 +120,7 @@ Similar to `key`, specify it within the [`definePageMeta`](/docs/4.x/api/utils/d
 
 ## `transition`
 
-:read-more{to="/docs/getting-started/transitions"}
+:read-more{to="/docs/4.x/getting-started/transitions"}
 
 ## `validate`
 

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/4.x/api/composables/use-runtime-config) without any import.
 
-:read-more{to="/docs/guide/going-further/runtime-config"}
+:read-more{to="/docs/4.x/guide/going-further/runtime-config"}
 
 ## Migration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.1.3-29313364.98ecc620",
+  "version": "4.1.3-29314777.50febbbb",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",