@nuxt/docs 3.19.2 → 3.19.3

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

@@ -15,7 +15,7 @@ With Nuxt Kit you can also add your own auto-imports. `addImports` and `addImpor
 These utilities are powered by [`unimport`](https://github.com/unjs/unimport), which provides the underlying auto-import mechanism used in Nuxt.
 
 ::note
-These functions are designed for registering your own utils, composables and Vue APIs. For pages, components and plugins, please refer to the specific sections: [Pages](/docs/api/kit/pages), [Components](/docs/api/kit/components), [Plugins](/docs/api/kit/plugins).
+These functions are designed for registering your own utils, composables and Vue APIs. For pages, components and plugins, please refer to the specific sections: [Pages](/docs/3.x/api/kit/pages), [Components](/docs/3.x/api/kit/components), [Plugins](/docs/3.x/api/kit/plugins).
 ::
 
 ::tip{icon="i-lucide-video" to="https://vueschool.io/lessons/expanding-nuxt-s-auto-imports?friend=nuxt" target="_blank"}
@@ -29,22 +29,22 @@ Add imports to the Nuxt application. It makes your imports available in the Nuxt
 ### Usage
 
 ```ts twoslash
-import { defineNuxtModule, addImports } from "@nuxt/kit";
+import { addImports, defineNuxtModule } from '@nuxt/kit'
 
 export default defineNuxtModule({
-  setup(options, nuxt) {
+  setup (options, nuxt) {
     const names = [
       'useStoryblok',
       'useStoryblokApi',
       'useStoryblokBridge',
       'renderRichText',
-      'RichTextSchema'
+      'RichTextSchema',
     ]
 
-    names.forEach((name) =>
-      addImports({ name, as: name, from: '@storyblok/vue' })
+    names.forEach(name =>
+      addImports({ name, as: name, from: '@storyblok/vue' }),
     )
-  }
+  },
 })
 ```
 
@@ -76,14 +76,14 @@ Add imports from a directory to the Nuxt application. It will automatically impo
 ### Usage
 
 ```ts twoslash
-import { defineNuxtModule, addImportsDir, createResolver } from '@nuxt/kit'
+import { addImportsDir, createResolver, defineNuxtModule } from '@nuxt/kit'
 
 export default defineNuxtModule({
   meta: {
     name: '@vueuse/motion',
     configKey: 'motion',
   },
-  setup(options, nuxt) {
+  setup (options, nuxt) {
     const resolver = createResolver(import.meta.url)
     addImportsDir(resolver.resolve('./runtime/composables'))
   },
@@ -110,10 +110,10 @@ Add listed imports to the Nuxt application.
 ### Usage
 
 ```ts twoslash
-import { defineNuxtModule, addImportsSources } from '@nuxt/kit'
+import { addImportsSources, defineNuxtModule } from '@nuxt/kit'
 
 export default defineNuxtModule({
-  setup() {
+  setup () {
     addImportsSources({
       from: 'h3',
       imports: [
@@ -121,10 +121,10 @@ export default defineNuxtModule({
         'getQuery',
         'getRouterParams',
         'readBody',
-        'sendRedirect'
+        'sendRedirect',
       ],
     })
-  }
+  },
 })
 ```
 

package/3.api/5.kit/5.components.md

@@ -26,13 +26,13 @@ export default defineNuxtModule({
     name: '@nuxt/ui',
     configKey: 'ui',
   },
-  setup() {
+  setup () {
     addComponentsDir({
       path: resolve('./runtime/components'),
       prefix: 'U',
-      pathPrefix: false
+      pathPrefix: false,
     })
-  }
+  },
 })
 ```
 
@@ -58,7 +58,7 @@ function addComponentsDir (dir: ComponentsDir, opts: { prepend?: boolean } = {})
 | `isAsync`          | `boolean`                    | `false`  | This flag indicates, component should be loaded async (with a separate chunk) regardless of using Lazy prefix or not. |
 | `extendComponent`  | `(component: Component) => Promise<Component \| void> \| (Component \| void)`{lang="ts"} | `false`  | A function that will be called for each component found in the directory. It accepts a component object and should return a component object or a promise that resolves to a component object. |
 | `global`           | `boolean`                    | `false`  | If enabled, registers components to be globally available.                                                      |
-| `island`           | `boolean`                    | `false`  | If enabled, registers components as islands. You can read more about islands in [`<NuxtIsland/>`](/docs/api/components/nuxt-island#nuxtisland) component description. |
+| `island`           | `boolean`                    | `false`  | If enabled, registers components as islands. You can read more about islands in [`<NuxtIsland/>`](/docs/3.x/api/components/nuxt-island#nuxtisland) component description. |
 | `watch`            | `boolean`                    | `false`  | Watch specified path for changes, including file additions and file deletions.                                  |
 | `extensions`       | `string[]`                   | `false`  | Extensions supported by Nuxt builder.                                                                          |
 | `transpile`        | `'auto' \| boolean`{lang="ts"} | `false`  | Transpile specified path using build.transpile. If set to `'auto'`, it will set `transpile: true` if `node_modules/` is in path. |
@@ -76,14 +76,14 @@ Register a component to be automatically imported.
 ### Usage
 
 ```ts
-import { defineNuxtModule, createResolver, addComponent } from '@nuxt/kit'
+import { addComponent, createResolver, defineNuxtModule } from '@nuxt/kit'
 
 export default defineNuxtModule({
   meta: {
     name: '@nuxt/image',
     configKey: 'image',
   },
-  async setup() {
+  setup () {
     const resolver = createResolver(import.meta.url)
 
     addComponent({
@@ -121,7 +121,7 @@ function addComponent (options: AddComponentOptions): void
 | `prefetch`         | `boolean`                    | `false`  | These properties (prefetch/preload) are used in production to configure how components with Lazy prefix are handled by webpack via its magic comments. Learn more on [webpack documentation](https://webpack.js.org/api/module-methods/#magic-comments) |  
 | `preload`          | `boolean`                    | `false`  | These properties (prefetch/preload) are used in production to configure how components with Lazy prefix are handled by webpack via its magic comments. Learn more on [webpack documentation](https://webpack.js.org/api/module-methods/#magic-comments) |
 | `global`           | `boolean`                    | `false`  | If enabled, registers component to be globally available.                                                        |
-| `island`           | `boolean`                    | `false`  | If enabled, registers component as island. You can read more about islands in [`<NuxtIsland/>`](/docs/api/components/nuxt-island#nuxtisland) component description. |
+| `island`           | `boolean`                    | `false`  | If enabled, registers component as island. You can read more about islands in [`<NuxtIsland/>`](/docs/3.x/api/components/nuxt-island#nuxtisland) component description. |
 | `mode`             | `'client' \| 'server' \| 'all'`{lang="ts"} | `false`  | This options indicates if component should render on client, server or both. By default, it will render on both client and server. |
 | `priority`         | `number`                     | `false`  | Priority of the component, if multiple components have the same name, the one with the highest priority will be used. |
 

package/3.api/5.kit/6.context.md

@@ -37,7 +37,7 @@ const setupSomeFeature = () => {
 // @errors: 2391
 import type { Nuxt } from '@nuxt/schema'
 // ---cut---
-function useNuxt(): Nuxt
+function useNuxt (): Nuxt
 ```
 
 ### Return Value
@@ -114,7 +114,7 @@ function setupSomething () {
 // @errors: 2391
 import type { Nuxt } from '@nuxt/schema'
 // ---cut---
-function tryUseNuxt(): Nuxt | null
+function tryUseNuxt (): Nuxt | null
 ```
 
 ### Return Value
@@ -156,7 +156,7 @@ interface SiteConfig {
   title?: string
 }
 export const requireSiteConfig = (): SiteConfig => {
- return {}
+  return {}
 }
 // @filename: module.ts
 // ---cut---

package/3.api/5.kit/7.pages.md

@@ -39,7 +39,7 @@ export default defineNuxtModule({
 ### Type
 
 ```ts
-function extendPages(callback: (pages: NuxtPage[]) => void): void
+function extendPages (callback: (pages: NuxtPage[]) => void): void
 ```
 
 ### Parameters
@@ -104,7 +104,7 @@ export default defineNuxtModule({
 ### Type
 
 ```ts
-function extendRouteRules(route: string, rule: NitroRouteConfig, options?: ExtendRouteRulesOptions): void
+function extendRouteRules (route: string, rule: NitroRouteConfig, options?: ExtendRouteRulesOptions): void
 ```
 
 ### Parameters
@@ -113,7 +113,7 @@ function extendRouteRules(route: string, rule: NitroRouteConfig, options?: Exten
 **rule**: A route rule configuration to apply to the matched route.
 
 ::tip
-About route rules configurations, you can get more detail in [Hybrid Rendering > Route Rules](/docs/guide/concepts/rendering#route-rules).
+About route rules configurations, you can get more detail in [Hybrid Rendering > Route Rules](/docs/3.x/guide/concepts/rendering#route-rules).
 ::
 
 **options**: A object to pass to the route configuration. If `override` is set to `true`, it will override the existing route configuration.
@@ -126,10 +126,10 @@ About route rules configurations, you can get more detail in [Hybrid Rendering >
 
 Registers route middlewares to be available for all routes or for specific routes.
 
-Route middlewares can be also defined in plugins via [`addRouteMiddleware`](/docs/api/utils/add-route-middleware) composable.
+Route middlewares can be also defined in plugins via [`addRouteMiddleware`](/docs/3.x/api/utils/add-route-middleware) composable.
 
 ::tip
-Read more about route middlewares in the [Route middleware documentation](/docs/getting-started/routing#route-middleware).
+Read more about route middlewares in the [Route middleware documentation](/docs/3.x/getting-started/routing#route-middleware).
 ::
 
 ::tip{icon="i-lucide-video" to="https://vueschool.io/lessons/adding-route-rules-and-route-middlewares?friend=nuxt" target="_blank"}
@@ -157,7 +157,7 @@ export default defineNuxtModule({
 ```
 
 ```ts twoslash [runtime/auth.ts]
-function isAuthenticated(): boolean { return false }
+function isAuthenticated (): boolean { return false }
 // ---cut---
 export default defineNuxtRouteMiddleware((to, from) => {
   // isAuthenticated() is an example method verifying if a user is authenticated
@@ -172,7 +172,7 @@ export default defineNuxtRouteMiddleware((to, from) => {
 ### Type
 
 ```ts
-function addRouteMiddleware(input: NuxtMiddleware | NuxtMiddleware[], options?: AddRouteMiddlewareOptions): void
+function addRouteMiddleware (input: NuxtMiddleware | NuxtMiddleware[], options?: AddRouteMiddlewareOptions): void
 ```
 
 ### Parameters

package/3.api/5.kit/8.layout.md

@@ -15,7 +15,7 @@ Layouts is used to be a wrapper around your pages. It can be used to wrap your p
 Register template as layout and add it to the layouts.
 
 ::note
-In Nuxt 2 `error` layout can also be registered using this utility. In Nuxt 3+ `error` layout [replaced](/docs/getting-started/error-handling#rendering-an-error-page) with `error.vue` page in project root.
+In Nuxt 2 `error` layout can also be registered using this utility. In Nuxt 3+ `error` layout [replaced](/docs/3.x/getting-started/error-handling#rendering-an-error-page) with `error.vue` page in project root.
 ::
 
 ### Usage
@@ -38,7 +38,7 @@ export default defineNuxtModule({
 ### Type
 
 ```ts
-function addLayout(layout: NuxtTemplate | string, name: string): void
+function addLayout (layout: NuxtTemplate | string, name: string): void
 ```
 
 ### Parameters

package/3.api/5.kit/9.plugins.md

@@ -38,7 +38,7 @@ export default defineNuxtModule({
 ### Type
 
 ```ts
-function addPlugin(plugin: NuxtPlugin | string, options?: AddPluginOptions): NuxtPlugin
+function addPlugin (plugin: NuxtPlugin | string, options?: AddPluginOptions): NuxtPlugin
 ```
 
 ### Parameters
@@ -128,7 +128,7 @@ export default defineNuxtPlugin({
 ### Type
 
 ```ts
-function addPluginTemplate(pluginOptions: NuxtPluginTemplate, options?: AddPluginOptions): NuxtPlugin
+function addPluginTemplate (pluginOptions: NuxtPluginTemplate, options?: AddPluginOptions): NuxtPlugin
 ```
 
 ### Parameters
@@ -204,12 +204,13 @@ export default defineNuxtConfig({
 
 ```ts [#build/vue-app-config.mjs]
 import { defineNuxtPlugin } from '#app/nuxt'
+
 export default defineNuxtPlugin({
   name: 'nuxt:vue-app-config',
   enforce: 'pre',
   setup (nuxtApp) {
-    nuxtApp.vueApp.config["idPrefix"] = "nuxt"
-  }
+    nuxtApp.vueApp.config.idPrefix = 'nuxt'
+  },
 })
 ```
 
@@ -239,7 +240,7 @@ export default defineNuxtModule({
 })
 ```
 
-```ts [templates/plugin.ejs]
+```ejs [templates/plugin.ejs]
 import { VueFire, useSSRInitialState } from 'vuefire'
 import { defineNuxtPlugin } from '#imports'
 

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

@@ -30,7 +30,7 @@ Hook                   | Arguments           | Environment     | Description
 `page:loading:end`     | -                   | Client          | Called after `page:finish`
 `page:transition:finish`| `pageComponent?`    | Client          | After page transition [onAfterLeave](https://vuejs.org/guide/built-ins/transition.html#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/getting-started/transitions#view-transitions-api-experimental).
+`page:view-transition:start` | `transition`        | Client          | Called after `document.startViewTransition` is called when [experimental viewTransition support is enabled](/docs/3.x/getting-started/transitions#view-transitions-api-experimental).
 
 ## Nuxt Hooks (build time)
 
@@ -46,7 +46,7 @@ Hook                     | Arguments                  | Description
 `modules:done`           | -                          | Called during Nuxt initialization, after installing user modules.
 `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/guide/directory-structure/nuxt#virtual-file-system) (vfs).
+`app:templatesGenerated` | `app`                      | Called after templates are compiled into the [virtual file system](/docs/3.x/guide/directory-structure/nuxt#virtual-file-system) (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.

package/3.api/6.advanced/2.import-meta.md

@@ -49,12 +49,12 @@ const resolver = createResolver(import.meta.url)
 
 export default defineNuxtModule({
   meta: { name: 'myModule' },
-  setup() {
+  setup () {
     addComponent({
       name: 'MyModuleComponent',
       // Resolves to '/modules/my-module/components/MyModuleComponent.vue'
-      filePath: resolver.resolve('./components/MyModuleComponent.vue')
+      filePath: resolver.resolve('./components/MyModuleComponent.vue'),
     })
-  }
+  },
 })
 ```

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/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/3.x/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/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/3.x/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/guide/going-further/modules/#joining-nuxt-modules-and-nuxtjs) to `nuxt-modules`. While these modules have individual maintainers, they are not dependent on a single person.
+* [nuxt-modules/](https://github.com/nuxt-modules) - community-contributed and maintained modules and libraries. There is a [process to migrate a module](/docs/3.x/guide/going-further/modules/#joining-nuxt-modules-and-nuxtjs) to `nuxt-modules`. While these modules have individual maintainers, they are not dependent on a single person.
 * [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/community/reporting-bugs) for some things to do before opening an issue.
+* **Reporting bugs**: Check out [our guide](/docs/3.x/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.
 
@@ -100,9 +100,9 @@ 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/guide/going-further/modules), so it can be shared with others? We have [many excellent modules already](/modules), but there's always room for more.
+If you've built something with Nuxt that's cool, why not [extract it into a module](/docs/3.x/guide/going-further/modules), so it can be shared with others? We have [many excellent modules already](/modules), but there's always room for more.
 
-If you need help while building it, feel free to [check in with us](/docs/community/getting-help).
+If you need help while building it, feel free to [check in with us](/docs/3.x/community/getting-help).
 
 ### Make an RFC
 
@@ -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/guide/going-further/modules) for more information.
+Modules should follow the [Nuxt module template](https://github.com/nuxt/starter/tree/module). See [module guide](/docs/3.x/guide/going-further/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/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/3.x/guide/concepts/esm).
 
 #### What's Corepack
 

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/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/3.x/community/contribution), here are some specific points to make about contributions to the [`nuxt/nuxt`](https://github.com/nuxt/nuxt) repository.
 
 ## Monorepo Guide
 
@@ -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/community/contribution#documentation-style-guide).
+Make sure to make changes according to the [Documentation Style Guide](/docs/3.x/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/community/contribution#documentation-style-guide).
+Make sure to make changes according to the [Documentation Style Guide](/docs/3.x/community/contribution#documentation-style-guide).
 ::
 
 ### Quick Edits

package/5.community/6.roadmap.md

@@ -63,7 +63,7 @@ The current active version of [Nuxt](https://nuxt.com) is **v4** which is availa
 
 Nuxt 3 will continue to receive maintenance updates (both bug fixes and backports of features from Nuxt 4) until the end of January 2026.
 
-Each active version has its own nightly releases which are generated automatically. For more about enabling the Nuxt nightly release channel, see [the nightly release channel docs](/docs/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/3.x/guide/going-further/nightly-release-channel).
 
 Release                    |                                                                                                                                                                               | Initial release       | End Of Life                  | Docs
 -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ---------------------------- | ---------------------------------------

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/getting-started/introduction).
+If you're starting a fresh Nuxt 3 project, please skip this section and go to [Nuxt 3 Installation](/docs/3.x/getting-started/introduction).
 ::
 
 ::warning
-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.
+Nuxt Bridge provides identical features to Nuxt 3 ([docs](/docs/3.x/guide/concepts/auto-imports)) but there are some limitations, notably that [`useAsyncData`](/docs/3.x/api/composables/use-async-data) and [`useFetch`](/docs/3.x/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.
@@ -80,13 +80,13 @@ bun add -D @nuxt/bridge 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/guide/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/3.x/guide/directory-structure/nuxt-config) is also possible and recommended.
 
 ```ts [nuxt.config.ts]
 import { defineNuxtConfig } from '@nuxt/bridge'
 
 export default defineNuxtConfig({
-  bridge: false
+  bridge: false,
 })
 ```
 
@@ -116,22 +116,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/bridge/typescript)
+- [TypeScript](/docs/3.x/bridge/typescript)
 
-- [Migrate Legacy Composition API](/docs/bridge/bridge-composition-api)
+- [Migrate Legacy Composition API](/docs/3.x/bridge/bridge-composition-api)
 
-- [Plugins and Middleware](/docs/bridge/plugins-and-middleware)
+- [Plugins and Middleware](/docs/3.x/bridge/plugins-and-middleware)
 
-- [Migrate New Composition API](/docs/bridge/nuxt3-compatible-api)
+- [Migrate New Composition API](/docs/3.x/bridge/nuxt3-compatible-api)
 
-- [Meta Tags](/docs/bridge/meta)
+- [Meta Tags](/docs/3.x/bridge/meta)
 
-- [Runtime Config](/docs/bridge/runtime-config)
+- [Runtime Config](/docs/3.x/bridge/runtime-config)
 
-- [Nitro](/docs/bridge/nitro)
+- [Nitro](/docs/3.x/bridge/nitro)
 
-- [Vite](/docs/bridge/vite)
+- [Vite](/docs/3.x/bridge/vite)
 
 ## Migrate from CommonJS to ESM
 
-Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/docs/guide/concepts/esm) for more info and upgrading.
+Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/docs/3.x/guide/concepts/esm) for more info and upgrading.

package/6.bridge/10.configuration.md

@@ -11,6 +11,7 @@ You can check [bridge/src/module.ts](https://github.com/nuxt/bridge/blob/main/pa
 
 ```ts [nuxt.config.ts]
 import { defineNuxtConfig } from '@nuxt/bridge'
+
 export default defineNuxtConfig({
   bridge: {
 
@@ -63,7 +64,7 @@ export default defineNuxtConfig({
 
   vite: {
     // Config for Vite
-  }
+  },
 })
 ```
 

package/6.bridge/2.typescript.md

@@ -16,8 +16,8 @@ import { defineNuxtConfig } from '@nuxt/bridge'
 export default defineNuxtConfig({
   bridge: {
     typescript: true,
-    nitro: false // If migration to Nitro is complete, set to true
-  }
+    nitro: false, // If migration to Nitro is complete, set to true
+  },
 })
 ```
 

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/bridge/nuxt3-compatible-api#usecontext-and-withcontext).
+- `withContext` has been removed. See [below](/docs/3.x/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/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/3.x/bridge/nuxt3-compatible-api#ssrref-and-shallowssrref) to replace this.
 
 ### Set `bridge.capi`
 
@@ -47,8 +47,8 @@ import { defineNuxtConfig } from '@nuxt/bridge'
 export default defineNuxtConfig({
   bridge: {
     capi: true,
-    nitro: false // If migration to Nitro is complete, set to true
-  }
+    nitro: false, // If migration to Nitro is complete, set to true
+  },
 })
 ```
 
@@ -117,9 +117,9 @@ While this example is valid, Nuxt 3 introduces a new defineNuxtPlugin function t
 
 ### `useRouter` and `useRoute`
 
-Nuxt Bridge provides direct replacements for these composables via [`useRouter`](/docs/api/composables/use-router)  and `useRoute`.
+Nuxt Bridge provides direct replacements for these composables via [`useRouter`](/docs/3.x/api/composables/use-router)  and `useRoute`.
 
-The only key difference is that [`useRoute`](/docs/api/composables/use-route) no longer returns a computed property.
+The only key difference is that [`useRoute`](/docs/3.x/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,17 +7,17 @@ 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/guide/directory-structure/plugins).
+Plugins now take only one argument (`nuxtApp`). You can find out more in [the docs](/docs/3.x/guide/directory-structure/plugins).
 
-```js [plugins/hello.ts]
-export default defineNuxtPlugin(nuxtApp => {
+```ts [plugins/hello.ts]
+export default defineNuxtPlugin((nuxtApp) => {
   nuxtApp.provide('injected', () => 'my injected function')
   // now available on `nuxtApp.$injected`
 })
 ```
 
 ::note
-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.
+If you want to use the new Nuxt composables (such as [`useNuxtApp`](/docs/3.x/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/guide/directory-structure/middleware).
+Middleware now take only two argument (`to`, `from`). You can find out more in [the docs](/docs/3.x/guide/directory-structure/middleware).
 
 ```ts twoslash
 export default defineNuxtRouteMiddleware((to) => {
@@ -44,7 +44,7 @@ Use of `defineNuxtRouteMiddleware` is not supported outside of the middleware di
 
 ## definePageMeta
 
-You can also use [`definePageMeta`](/docs/api/utils/define-page-meta) in Nuxt Bridge.
+You can also use [`definePageMeta`](/docs/3.x/api/utils/define-page-meta) in Nuxt Bridge.
 
 You can be enabled with the `macros.pageMeta` option in your configuration file
 
@@ -54,9 +54,9 @@ import { defineNuxtConfig } from '@nuxt/bridge'
 export default defineNuxtConfig({
   bridge: {
     macros: {
-      pageMeta: true
-    }
-  }
+      pageMeta: true,
+    },
+  },
 })
 ```