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

package/1.getting-started/01.introduction.md

@@ -12,14 +12,14 @@ We made everything so you can start writing `.vue` files from the beginning whil
 Nuxt has no vendor lock-in, allowing you to deploy your application [**everywhere, even on the edge**](/blog/nuxt-on-the-edge).
 
 ::tip
-If you want to play around with Nuxt in your browser, you can [try it out in one of our online sandboxes](/docs/4.x/getting-started/installation#play-online).
+If you want to play around with Nuxt in your browser, you can [try it out in one of our online sandboxes](/docs/getting-started/installation#play-online).
 ::
 
 ## Automation and Conventions
 
 Nuxt uses conventions and an opinionated directory structure to automate repetitive tasks and allow developers to focus on pushing features. The configuration file can still customize and override its default behaviors.
 
-- **File-based routing:** define routes based on the structure of your [`app/pages/` directory](/docs/4.x/directory-structure/app/pages). This can make it easier to organize your application and avoid the need for manual route configuration.
+- **File-based routing:** define routes based on the structure of your [`app/pages/` directory](/docs/directory-structure/app/pages). This can make it easier to organize your application and avoid the need for manual route configuration.
 - **Code splitting:** Nuxt automatically splits your code into smaller chunks, which can help reduce the initial load time of your application.
 - **Server-side rendering out of the box:** Nuxt comes with built-in SSR capabilities, so you don't have to set up a separate server yourself.
 - **Auto-imports:** write Vue composables and components in their respective directories and use them without having to import them with the benefits of tree-shaking and optimized JS bundles.
@@ -44,29 +44,29 @@ Overall, server-side rendering can provide a faster and more efficient user expe
 As Nuxt is a versatile framework, it gives you the possibility to statically render your whole application to a static hosting with `nuxt generate`,
 disable SSR globally with the `ssr: false` option or leverage hybrid rendering by setting up the `routeRules` option.
 
-:read-more{title="Nuxt rendering modes" to="/docs/4.x/guide/concepts/rendering"}
+:read-more{title="Nuxt rendering modes" to="/docs/guide/concepts/rendering"}
 
 ### Server engine
 
-The Nuxt server engine [Nitro](https://nitro.build/) unlocks new full-stack capabilities.
+The Nuxt server engine, [Nitro](https://nitro.build/), unlocks new full-stack capabilities.
 
-In development, it uses Rollup and Node.js workers for your server code and context isolation. It also generates your server API by reading files in `server/api/` and server middleware from `server/middleware/`.
+In development, it uses Rollup and Node.js workers for your server code and context isolation. It also generates your server API by reading files from `server/api/` and server middleware from `server/middleware/`.
 
 In production, Nitro builds your app and server into one universal `.output` directory. This output is light: minified and removed from any Node.js modules (except polyfills). You can deploy this output on any system supporting JavaScript, from Node.js, Serverless, Workers, Edge-side rendering or purely static.
 
-:read-more{title="Nuxt server engine" to="/docs/4.x/guide/concepts/server-engine"}
+:read-more{title="Nuxt server engine" to="/docs/guide/concepts/server-engine"}
 
 ### Production-ready
 
 A Nuxt application can be deployed on a Node or Deno server, pre-rendered to be hosted in static environments, or deployed to serverless and edge providers.
 
-:read-more{title="Deployment section" to="/docs/4.x/getting-started/deployment"}
+:read-more{title="Deployment section" to="/docs/getting-started/deployment"}
 
 ### Modular
 
 A module system allows you to extend Nuxt with custom features and integrations with third-party services.
 
-:read-more{title="Nuxt Modules Concept" to="/docs/4.x/guide/concepts/modules"}
+:read-more{title="Nuxt Modules Concept" to="/docs/guide/concepts/modules"}
 
 ### Architecture
 

package/1.getting-started/02.installation.md

@@ -108,9 +108,7 @@ Well done! A browser window should automatically open for <http://localhost:3000
 ::
 
 ::tip{icon="i-lucide-container"}
-If you're using Docker or want a consistent development environment across machines, consider using a dev container.
-
-[Learn more about dev containers](/docs/4.x/guide/best-practices/devcontainers)
+If you're using Docker or want a consistent development environment across machines, consider using a dev container. [Learn more about dev containers.](/docs/guide/best-practices/devcontainers)
 ::
 
 ::
@@ -119,4 +117,4 @@ If you're using Docker or want a consistent development environment across machi
 
 Now that you've created your Nuxt project, you are ready to start building your application.
 
-:read-more{title="Nuxt Concepts" to="/docs/4.x/guide/concepts"}
+:read-more{title="Nuxt Concepts" to="/docs/guide/concepts"}

package/1.getting-started/03.configuration.md

@@ -4,11 +4,11 @@ description: Nuxt is configured with sensible defaults to make you productive.
 navigation.icon: i-lucide-cog
 ---
 
-By default, Nuxt is configured to cover most use cases. The [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) file can override or extend this default configuration.
+By default, Nuxt is configured to cover most use cases. The [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) file can override or extend this default configuration.
 
 ## Nuxt Configuration
 
-The [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) file is located at the root of a Nuxt project and can override or extend the application's behavior.
+The [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) file is located at the root of a Nuxt project and can override or extend the application's behavior.
 
 A minimal configuration file exports the `defineNuxtConfig` function containing an object with your configuration. The `defineNuxtConfig` helper is globally available without import.
 
@@ -20,7 +20,7 @@ export default defineNuxtConfig({
 
 This file will often be mentioned in the documentation, for example to add custom scripts, register modules or change rendering modes.
 
-::read-more{to="/docs/4.x/api/configuration/nuxt-config"}
+::read-more{to="/docs/api/configuration/nuxt-config"}
 Every option is described in the **Configuration Reference**.
 ::
 
@@ -88,7 +88,7 @@ NUXT_API_SECRET=api_secret_token
 
 ::
 
-These variables are exposed to the rest of your application using the [`useRuntimeConfig()`](/docs/4.x/api/composables/use-runtime-config) composable.
+These variables are exposed to the rest of your application using the [`useRuntimeConfig()`](/docs/api/composables/use-runtime-config) composable.
 
 ```vue [app/pages/index.vue]
 <script setup lang="ts">
@@ -96,7 +96,7 @@ const runtimeConfig = useRuntimeConfig()
 </script>
 ```
 
-:read-more{to="/docs/4.x/guide/going-further/runtime-config"}
+:read-more{to="/docs/guide/going-further/runtime-config"}
 
 ## App Configuration
 
@@ -116,7 +116,7 @@ export default defineAppConfig({
 })
 ```
 
-These variables are exposed to the rest of your application using the [`useAppConfig`](/docs/4.x/api/composables/use-app-config) composable.
+These variables are exposed to the rest of your application using the [`useAppConfig`](/docs/api/composables/use-app-config) composable.
 
 ```vue [app/pages/index.vue]
 <script setup lang="ts">
@@ -124,7 +124,7 @@ const appConfig = useAppConfig()
 </script>
 ```
 
-:read-more{to="/docs/4.x/directory-structure/app/app-config"}
+:read-more{to="/docs/directory-structure/app/app-config"}
 
 ## `runtimeConfig` vs. `app.config`
 
@@ -145,20 +145,20 @@ As stated above, `runtimeConfig` and `app.config` are both used to expose variab
 
 ## External Configuration Files
 
-Nuxt uses [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) file as the single source of truth for configurations and skips reading external configuration files. During the course of building your project, you may have a need to configure those. The following table highlights common configurations and, where applicable, how they can be configured with Nuxt.
+Nuxt uses [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) file as the single source of truth for configurations and skips reading external configuration files. During the course of building your project, you may have a need to configure those. The following table highlights common configurations and, where applicable, how they can be configured with Nuxt.
 
 | Name                              | Config File             | How To Configure                                                          |
 |-----------------------------------|-------------------------|---------------------------------------------------------------------------|
-| [Nitro](https://nitro.build)      | ~~`nitro.config.ts`~~   | Use [`nitro`](/docs/4.x/api/nuxt-config#nitro) key in `nuxt.config`       |
-| [PostCSS](https://postcss.org)    | ~~`postcss.config.js`~~ | Use [`postcss`](/docs/4.x/api/nuxt-config#postcss) key in `nuxt.config`   |
-| [Vite](https://vite.dev)          | ~~`vite.config.ts`~~    | Use [`vite`](/docs/4.x/api/nuxt-config#vite) key in `nuxt.config`         |
-| [webpack](https://webpack.js.org) | ~~`webpack.config.ts`~~ | Use [`webpack`](/docs/4.x/api/nuxt-config#webpack-1) key in `nuxt.config` |
+| [Nitro](https://nitro.build)      | ~~`nitro.config.ts`~~   | Use [`nitro`](/docs/api/nuxt-config#nitro) key in `nuxt.config`       |
+| [PostCSS](https://postcss.org)    | ~~`postcss.config.js`~~ | Use [`postcss`](/docs/api/nuxt-config#postcss) key in `nuxt.config`   |
+| [Vite](https://vite.dev)          | ~~`vite.config.ts`~~    | Use [`vite`](/docs/api/nuxt-config#vite) key in `nuxt.config`         |
+| [webpack](https://webpack.js.org) | ~~`webpack.config.ts`~~ | Use [`webpack`](/docs/api/nuxt-config#webpack-1) key in `nuxt.config` |
 
 Here is a list of other common config files:
 
 | Name                                         | Config File           | How To Configure                                                              |
 |----------------------------------------------|-----------------------|-------------------------------------------------------------------------------|
-| [TypeScript](https://www.typescriptlang.org) | `tsconfig.json`       | [More Info](/docs/4.x/directory-structure/tsconfig)                           |
+| [TypeScript](https://www.typescriptlang.org) | `tsconfig.json`       | [More Info](/docs/directory-structure/tsconfig)                           |
 | [ESLint](https://eslint.org)                 | `eslint.config.js`    | [More Info](https://eslint.org/docs/latest/use/configure/configuration-files) |
 | [Prettier](https://prettier.io)              | `prettier.config.js`  | [More Info](https://prettier.io/docs/configuration.html)                      |
 | [Stylelint](https://stylelint.io)            | `stylelint.config.js` | [More Info](https://stylelint.io/user-guide/configure/)                       |
@@ -187,7 +187,7 @@ export default defineNuxtConfig({
 })
 ```
 
-:read-more{to="/docs/4.x/api/configuration/nuxt-config#vue"}
+:read-more{to="/docs/api/configuration/nuxt-config#vue"}
 
 ### With webpack
 
@@ -205,7 +205,7 @@ export default defineNuxtConfig({
 })
 ```
 
-:read-more{to="/docs/4.x/api/configuration/nuxt-config#loaders"}
+:read-more{to="/docs/api/configuration/nuxt-config#loaders"}
 
 ### Enabling Experimental Vue Features
 
@@ -223,4 +223,4 @@ export default defineNuxtConfig({
 
 Since Nuxt 3.9 and Vue 3.4, `reactivityTransform` has been moved from Vue to Vue Macros which has a [Nuxt integration](https://vue-macros.dev/guide/nuxt-integration.html).
 
-:read-more{to="/docs/4.x/api/configuration/nuxt-config#vue-1"}
+:read-more{to="/docs/api/configuration/nuxt-config#vue-1"}

package/1.getting-started/04.views.md

@@ -26,7 +26,7 @@ If you are familiar with Vue, you might wonder where `main.js` is (the file that
 
 ![Components are reusable pieces of UI](/assets/docs/getting-started/views/components.svg)
 
-Most components are reusable pieces of the user interface, like buttons and menus. In Nuxt, you can create these components in the [`app/components/`](/docs/4.x/directory-structure/app/components) directory, and they will be automatically available across your application without having to explicitly import them.
+Most components are reusable pieces of the user interface, like buttons and menus. In Nuxt, you can create these components in the [`app/components/`](/docs/directory-structure/app/components) directory, and they will be automatically available across your application without having to explicitly import them.
 
 ::code-group
 
@@ -55,9 +55,9 @@ Most components are reusable pieces of the user interface, like buttons and menu
 
 ![Pages are views tied to a specific route](/assets/docs/getting-started/views/pages.svg)
 
-Pages represent views for each specific route pattern. Every file in the [`app/pages/`](/docs/4.x/directory-structure/app/pages) directory represents a different route displaying its content.
+Pages represent views for each specific route pattern. Every file in the [`app/pages/`](/docs/directory-structure/app/pages) directory represents a different route displaying its content.
 
-To use pages, create an `app/pages/index.vue` file and add `<NuxtPage />` component to the [`app/app.vue`](/docs/4.x/directory-structure/app/app) (or remove `app/app.vue` for default entry). You can now create more pages and their corresponding routes by adding new files in the [`app/pages/`](/docs/4.x/directory-structure/app/pages) directory.
+To use pages, create an `app/pages/index.vue` file and add `<NuxtPage />` component to the [`app/app.vue`](/docs/directory-structure/app/app) (or remove `app/app.vue` for default entry). You can now create more pages and their corresponding routes by adding new files in the [`app/pages/`](/docs/directory-structure/app/pages) directory.
 
 ::code-group
 
@@ -82,7 +82,7 @@ To use pages, create an `app/pages/index.vue` file and add `<NuxtPage />` compon
 
 ::
 
-:read-more{title="Routing Section" to="/docs/4.x/getting-started/routing"}
+:read-more{title="Routing Section" to="/docs/getting-started/routing"}
 
 ## Layouts
 
@@ -91,7 +91,7 @@ To use pages, create an `app/pages/index.vue` file and add `<NuxtPage />` compon
 Layouts are wrappers around pages that contain a common User Interface for several pages, such as header and footer displays. Layouts are Vue files using `<slot />` components to display the **page** content. The `app/layouts/default.vue` file will be used by default. Custom layouts can be set as part of your page metadata.
 
 ::note
-If you only have a single layout in your application, we recommend using [`app/app.vue`](/docs/4.x/directory-structure/app/app) with [`<NuxtPage />`](/docs/4.x/api/components/nuxt-page) instead.
+If you only have a single layout in your application, we recommend using [`app/app.vue`](/docs/directory-structure/app/app) with [`<NuxtPage />`](/docs/api/components/nuxt-page) instead.
 ::
 
 ::code-group
@@ -137,12 +137,12 @@ If you only have a single layout in your application, we recommend using [`app/a
 
 ::
 
-If you want to create more layouts and learn how to use them in your pages, find more information in the [Layouts section](/docs/4.x/directory-structure/app/layouts).
+If you want to create more layouts and learn how to use them in your pages, find more information in the [Layouts section](/docs/directory-structure/app/layouts).
 
 ## Advanced: Extending the HTML Template
 
 ::note
-If you only need to modify the `<head>`, you can refer to the [SEO and meta section](/docs/4.x/getting-started/seo-meta).
+If you only need to modify the `<head>`, you can refer to the [SEO and meta section](/docs/getting-started/seo-meta).
 ::
 
 You can have full control over the HTML template by adding a Nitro plugin that registers a hook.
@@ -162,4 +162,4 @@ export default defineNitroPlugin((nitroApp) => {
 })
 ```
 
-:read-more{to="/docs/4.x/guide/going-further/hooks"}
+:read-more{to="/docs/guide/going-further/hooks"}

package/1.getting-started/05.assets.md

@@ -6,14 +6,14 @@ navigation.icon: i-lucide-image
 
 Nuxt uses two directories to handle assets like stylesheets, fonts or images.
 
-- The [`public/`](/docs/4.x/directory-structure/public) directory content is served at the server root as-is.
-- The [`app/assets/`](/docs/4.x/directory-structure/app/assets) directory contains by convention every asset that you want the build tool (Vite or webpack) to process.
+- The [`public/`](/docs/directory-structure/public) directory content is served at the server root as-is.
+- The [`app/assets/`](/docs/directory-structure/app/assets) directory contains by convention every asset that you want the build tool (Vite or webpack) to process.
 
 ## Public Directory
 
-The [`public/`](/docs/4.x/directory-structure/public) directory is used as a public server for static assets publicly available at a defined URL of your application.
+The [`public/`](/docs/directory-structure/public) directory is used as a public server for static assets publicly available at a defined URL of your application.
 
-You can get a file in the [`public/`](/docs/4.x/directory-structure/public) directory from your application's code or from a browser by the root URL `/`.
+You can get a file in the [`public/`](/docs/directory-structure/public) directory from your application's code or from a browser by the root URL `/`.
 
 ### Example
 
@@ -32,9 +32,9 @@ For example, referencing an image file in the `public/img/` directory, available
 
 Nuxt uses [Vite](https://vite.dev/guide/assets) (default) or [webpack](https://webpack.js.org/guides/asset-management/) to build and bundle your application. The main function of these build tools is to process JavaScript files, but they can be extended through [plugins](https://vite.dev/plugins/) (for Vite) or [loaders](https://webpack.js.org/loaders/) (for webpack) to process other kinds of assets, like stylesheets, fonts or SVGs. This step transforms the original file, mainly for performance or caching purposes (such as stylesheet minification or browser cache invalidation).
 
-By convention, Nuxt uses the [`app/assets/`](/docs/4.x/directory-structure/app/assets) directory to store these files but there is no auto-scan functionality for this directory, and you can use any other name for it.
+By convention, Nuxt uses the [`app/assets/`](/docs/directory-structure/app/assets) directory to store these files but there is no auto-scan functionality for this directory, and you can use any other name for it.
 
-In your application's code, you can reference a file located in the [`app/assets/`](/docs/4.x/directory-structure/app/assets) directory by using the `~/assets/` path.
+In your application's code, you can reference a file located in the [`app/assets/`](/docs/directory-structure/app/assets) directory by using the `~/assets/` path.
 
 ### Example
 
@@ -50,12 +50,12 @@ For example, referencing an image file that will be processed if a build tool is
 ```
 
 ::note
-Nuxt won't serve files in the [`app/assets/`](/docs/4.x/directory-structure/app/assets) directory at a static URL like `/assets/my-file.png`. If you need a static URL, use the [`public/`](/docs/4.x/getting-started/assets#public-directory) directory.
+Nuxt won't serve files in the [`app/assets/`](/docs/directory-structure/app/assets) directory at a static URL like `/assets/my-file.png`. If you need a static URL, use the [`public/`](/docs/getting-started/assets#public-directory) directory.
 ::
 
 ### Static vs. Dynamic `src`
 
-When an `src` is a static string literal in your template, the build tool rewrites it into a runtime helper that resolves the final URL. A public path such as `/img/nuxt.png` is wrapped so that your [`app.baseURL`](/docs/4.x/api/nuxt-config#baseurl) is applied when the page renders, and a bundled path such as `~/assets/img/nuxt.png` additionally becomes an import that resolves to the hashed output file.
+When an `src` is a static string literal in your template, the build tool rewrites it into a runtime helper that resolves the final URL. A public path such as `/img/nuxt.png` is wrapped so that your [`app.baseURL`](/docs/api/nuxt-config#baseurl) is applied when the page renders, and a bundled path such as `~/assets/img/nuxt.png` additionally becomes an import that resolves to the hashed output file.
 
 ```vue
 <template>
@@ -76,13 +76,13 @@ A bound `:src` whose value is assembled at runtime is opaque to the build tool,
 </template>
 ```
 
-A runtime-built public path like `/img/${name}.png` is therefore **not** prefixed with [`app.baseURL`](/docs/4.x/api/nuxt-config#baseurl). If your application is deployed below the origin root, prefix it yourself with [`useRuntimeConfig().app.baseURL`](/docs/4.x/api/composables/use-runtime-config) (for example via [`joinURL`](https://github.com/unjs/ufo#joinurl)).
+A runtime-built public path like `/img/${name}.png` is therefore **not** prefixed with [`app.baseURL`](/docs/api/nuxt-config#baseurl). If your application is deployed below the origin root, prefix it yourself with [`useRuntimeConfig().app.baseURL`](/docs/api/composables/use-runtime-config) (for example via [`joinURL`](https://github.com/unjs/ufo#joinurl)).
 
 The sections below cover how to handle each case when the path is only known at runtime.
 
 #### Public Assets
 
-If the files do not need to be processed or hashed, put them in the [`public/`](/docs/4.x/directory-structure/public) directory and reference them by URL:
+If the files do not need to be processed or hashed, put them in the [`public/`](/docs/directory-structure/public) directory and reference them by URL:
 
 ```vue [app/app.vue]
 <script setup lang="ts">

package/1.getting-started/06.styling.md

@@ -9,7 +9,7 @@ You can use CSS preprocessors, CSS frameworks, UI libraries and Nuxt modules to
 
 ## Local Stylesheets
 
-If you're writing local stylesheets, the natural place to put them is the [`app/assets/` directory](/docs/4.x/directory-structure/app/assets).
+If you're writing local stylesheets, the natural place to put them is the [`app/assets/` directory](/docs/directory-structure/app/assets).
 
 ### Importing Within Components
 
@@ -37,7 +37,7 @@ The stylesheets will be inlined in the HTML rendered by Nuxt.
 ### The CSS Property
 
 You can also use the `css` property in the Nuxt configuration.
-The natural place for your stylesheets is the [`app/assets/` directory](/docs/4.x/directory-structure/app/assets). You can then reference its path and Nuxt will include it to all the pages of your application.
+The natural place for your stylesheets is the [`app/assets/` directory](/docs/directory-structure/app/assets). You can then reference its path and Nuxt will include it to all the pages of your application.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -125,7 +125,7 @@ export default defineNuxtConfig({
 
 You can include external stylesheets in your application by adding a link element in the head section of your nuxt.config file. You can achieve this result using different methods. Note that local stylesheets can also be included this way.
 
-You can manipulate the head with the [`app.head`](/docs/4.x/api/nuxt-config#head) property of your Nuxt configuration:
+You can manipulate the head with the [`app.head`](/docs/api/nuxt-config#head) property of your Nuxt configuration:
 
 ```ts twoslash [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -141,7 +141,7 @@ export default defineNuxtConfig({
 
 You can use the useHead composable to dynamically set a value in your head in your code.
 
-:read-more{to="/docs/4.x/api/composables/use-head"}
+:read-more{to="/docs/api/composables/use-head"}
 
 ```ts twoslash
 useHead({
@@ -286,7 +286,7 @@ This is an experimental option and you should refer to the Vite documentation an
 
 ## Single File Components (SFC) Styling
 
-One of the best things about Vue and SFC is how great it is at naturally dealing with styling. You can directly write CSS or preprocessor code in the style block of your components file, therefore you will have fantastic developer experience without having to use something like CSS-in-JS. However if you wish to use CSS-in-JS, you can find 3rd party libraries and modules that support it, such as [pinceau](https://github.com/Tahul/pinceau).
+One of the best things about Vue and SFC is how great it is at naturally dealing with styling. You can directly write CSS or preprocessor code in the style block of your components file, therefore you will have a fantastic developer experience without having to use something like CSS-in-JS. However if you wish to use CSS-in-JS, you can find 3rd party libraries and modules that support it, such as [pinceau](https://github.com/Tahul/pinceau).
 
 You can refer to the [Vue docs](https://vuejs.org/api/sfc-css-features) for a comprehensive reference about styling components in SFC.
 
@@ -362,7 +362,7 @@ Refer to the [Vue docs](https://vuejs.org/guide/essentials/class-and-style) for
 
 ### Dynamic Styles With `v-bind`
 
-You can reference JavaScript variable and expression within your style blocks with the v-bind function.
+You can reference JavaScript variables and expressions within your style blocks with the v-bind function.
 The binding will be dynamic, meaning that if the variable value changes, the style will be updated.
 
 ```vue
@@ -504,7 +504,7 @@ Use different styles for different layouts.
 </style>
 ```
 
-:read-more{to="/docs/4.x/directory-structure/app/layouts"}
+:read-more{to="/docs/directory-structure/app/layouts"}
 
 ## Third Party Libraries And Modules
 
@@ -521,7 +521,7 @@ Here are a few modules to help you get started:
 - [Nuxt UI](https://ui.nuxt.com): A UI Library for Modern Web Apps
 - [Panda CSS](https://panda-css.com/docs/installation/nuxt): CSS-in-JS engine that generates atomic CSS at build time
 
-Nuxt modules provide you with a good developer experience out of the box, but remember that if your favorite tool doesn't have a module, it doesn't mean that you can't use it with Nuxt! You can configure it yourself for your own project. Depending on the tool, you might need to use a [Nuxt plugin](/docs/4.x/directory-structure/app/plugins) and/or [make your own module](/docs/4.x/guide/modules). Share them with the [community](/modules) if you do!
+Nuxt modules provide you with a good developer experience out of the box, but remember that if your favorite tool doesn't have a module, it doesn't mean that you can't use it with Nuxt! You can configure it yourself for your own project. Depending on the tool, you might need to use a [Nuxt plugin](/docs/directory-structure/app/plugins) and/or [make your own module](/docs/guide/modules). Share them with the [community](/modules) if you do!
 
 ### Easily Load Webfonts
 
@@ -533,9 +533,9 @@ If you are using [UnoCSS](https://unocss.dev/integrations/nuxt), note that it co
 
 ### Transitions
 
-Nuxt comes with the same `<Transition>` element that Vue has, and also has support for the experimental [View Transitions API](/docs/4.x/getting-started/transitions#view-transitions-api-experimental).
+Nuxt comes with the same `<Transition>` element that Vue has, and also has support for the experimental [View Transitions API](/docs/getting-started/transitions#view-transitions-api-experimental).
 
-:read-more{to="/docs/4.x/getting-started/transitions"}
+:read-more{to="/docs/getting-started/transitions"}
 
 ### Font Advanced Optimization
 

package/1.getting-started/07.routing.md

@@ -4,10 +4,10 @@ description: Nuxt file-system routing creates a route for every file in the page
 navigation.icon: i-lucide-milestone
 ---
 
-One core feature of Nuxt is the file system router. Every Vue file inside the [`app/pages/`](/docs/4.x/directory-structure/app/pages) directory creates a corresponding URL (or route) that displays the contents of the file. By using dynamic imports for each page, Nuxt leverages code-splitting to ship the minimum amount of JavaScript for the requested route.
+One core feature of Nuxt is the file system router. Every Vue file inside the [`app/pages/`](/docs/directory-structure/app/pages) directory creates a corresponding URL (or route) that displays the contents of the file. By using dynamic imports for each page, Nuxt leverages code-splitting to ship the minimum amount of JavaScript for the requested route.
 
 ::note
-Code-splitting is enabled by default and is recommended for most apps. If you have a specific reason to ship a single bundle instead, you can disable it in your [`nuxt.config`](/docs/4.x/api/nuxt-config):
+Code-splitting is enabled by default and is recommended for most apps. If you have a specific reason to ship a single bundle instead, you can disable it in your [`nuxt.config`](/docs/api/nuxt-config):
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -30,7 +30,7 @@ This ships all JavaScript in a single file. It is rarely beneficial — it usual
 
 ## Pages
 
-Nuxt routing is based on [vue-router](https://router.vuejs.org) and generates the routes from every component created in the [`app/pages/` directory](/docs/4.x/directory-structure/app/pages), based on their filename.
+Nuxt routing is based on [vue-router](https://router.vuejs.org) and generates the routes from every component created in the [`app/pages/` directory](/docs/directory-structure/app/pages), based on their filename.
 
 This file system routing uses naming conventions to create dynamic and nested routes:
 
@@ -65,13 +65,13 @@ This file system routing uses naming conventions to create dynamic and nested ro
 
 ::
 
-:read-more{to="/docs/4.x/directory-structure/app/pages"}
+:read-more{to="/docs/directory-structure/app/pages"}
 
 ## Navigation
 
-The [`<NuxtLink>`](/docs/4.x/api/components/nuxt-link) component links pages between them. It renders an `<a>` tag with the `href` attribute set to the route of the page. Once the application is hydrated, page transitions are performed in JavaScript by updating the browser URL. This prevents full-page refreshes and allows for animated transitions.
+The [`<NuxtLink>`](/docs/api/components/nuxt-link) component links pages between them. It renders an `<a>` tag with the `href` attribute set to the route of the page. Once the application is hydrated, page transitions are performed in JavaScript by updating the browser URL. This prevents full-page refreshes and allows for animated transitions.
 
-When a [`<NuxtLink>`](/docs/4.x/api/components/nuxt-link) enters the viewport on the client side, Nuxt will automatically prefetch components and payload (generated pages) of the linked pages ahead of time, resulting in faster navigation.
+When a [`<NuxtLink>`](/docs/api/components/nuxt-link) enters the viewport on the client side, Nuxt will automatically prefetch components and payload (generated pages) of the linked pages ahead of time, resulting in faster navigation.
 
 ```vue [app/pages/index.vue]
 <template>
@@ -87,11 +87,11 @@ When a [`<NuxtLink>`](/docs/4.x/api/components/nuxt-link) enters the viewport on
 </template>
 ```
 
-:read-more{to="/docs/4.x/api/components/nuxt-link"}
+:read-more{to="/docs/api/components/nuxt-link"}
 
 ## Route Parameters
 
-The [`useRoute()`](/docs/4.x/api/composables/use-route) composable can be used in a `<script setup>` block or a `setup()` method of a Vue component to access the current route details.
+The [`useRoute()`](/docs/api/composables/use-route) composable can be used in a `<script setup>` block or a `setup()` method of a Vue component to access the current route details.
 
 ```vue twoslash [pages/posts/[id\\].vue]
 <script setup lang="ts">
@@ -102,7 +102,7 @@ console.log(route.params.id)
 </script>
 ```
 
-:read-more{to="/docs/4.x/api/composables/use-route"}
+:read-more{to="/docs/api/composables/use-route"}
 
 ## Route Middleware
 
@@ -113,14 +113,14 @@ Route middleware runs within the Vue part of your Nuxt app. Despite the similar
 ::
 
 ::important
-Route middleware does **not** run for server routes (e.g. `/api/*`) or other server requests. To apply middleware to these requests, use [server middleware](/docs/4.x/directory-structure/server#server-middleware) instead.
+Route middleware does **not** run for server routes (e.g. `/api/*`) or other server requests. To apply middleware to these requests, use [server middleware](/docs/directory-structure/server#server-middleware) instead.
 ::
 
 There are three kinds of route middleware:
 
 1. Anonymous (or inline) route middleware, which are defined directly in the pages where they are used.
-2. Named route middleware, which are placed in the [`app/middleware/`](/docs/4.x/directory-structure/app/middleware) directory and will be automatically loaded via asynchronous import when used on a page. (**Note**: The route middleware name is normalized to kebab-case, so `someMiddleware` becomes `some-middleware`.)
-3. Global route middleware, which are placed in the [`app/middleware/`](/docs/4.x/directory-structure/app/middleware) directory (with a `.global` suffix) and will be automatically run on every route change.
+2. Named route middleware, which are placed in the [`app/middleware/`](/docs/directory-structure/app/middleware) directory and will be automatically loaded via asynchronous import when used on a page. (**Note**: The route middleware name is normalized to kebab-case, so `someMiddleware` becomes `some-middleware`.)
+3. Global route middleware, which are placed in the [`app/middleware/`](/docs/directory-structure/app/middleware) directory (with a `.global` suffix) and will be automatically run on every route change.
 
 Example of an `auth` middleware protecting the `/dashboard` page:
 
@@ -151,11 +151,11 @@ definePageMeta({
 
 ::
 
-:read-more{to="/docs/4.x/directory-structure/app/middleware"}
+:read-more{to="/docs/directory-structure/app/middleware"}
 
 ## Route Validation
 
-Nuxt offers route validation via the `validate` property in [`definePageMeta()`](/docs/4.x/api/utils/define-page-meta) in each page you wish to validate.
+Nuxt offers route validation via the `validate` property in [`definePageMeta()`](/docs/api/utils/define-page-meta) in each page you wish to validate.
 
 The `validate` property accepts the `route` as an argument. You can return a boolean value to determine whether or not this is a valid route to be rendered with this page. If you return `false`, this will cause a 404 error. You can also directly return an object with `status`/`statusText` to customize the error returned.
 
@@ -172,4 +172,4 @@ definePageMeta({
 </script>
 ```
 
-:read-more{to="/docs/4.x/api/utils/define-page-meta"}
+:read-more{to="/docs/api/utils/define-page-meta"}

package/1.getting-started/08.seo-meta.md

@@ -9,7 +9,7 @@ and numerous configuration options to manage your app's head and SEO meta tags.
 
 ## Nuxt Config
 
-Providing an [`app.head`](/docs/4.x/api/nuxt-config#head) property in your [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) allows you to statically customize the head for your entire app.
+Providing an [`app.head`](/docs/api/nuxt-config#head) property in your [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) allows you to statically customize the head for your entire app.
 
 ::important
 This method does not allow you to provide reactive data. We recommend using `useHead()` in `app.vue`.
@@ -34,7 +34,7 @@ export default defineNuxtConfig({
 ```
 
 ::note
-When you set [`app.cdnURL`](/docs/4.x/api/nuxt-config#cdnurl), assets in your [`public/`](/docs/4.x/directory-structure/public) directory (including `favicon.ico`) are served from that CDN. Nuxt resolves public assets against `cdnURL`, falling back to `app.baseURL`. However, a static `app.head` link such as `href: '/favicon.ico'` above is a literal path and is **not** resolved against `cdnURL`. To point the favicon at the resolved location, build the `href` from runtime config with [`useHead()`](/docs/4.x/api/composables/use-head) in `app.vue`:
+When you set [`app.cdnURL`](/docs/api/nuxt-config#cdnurl), assets in your [`public/`](/docs/directory-structure/public) directory (including `favicon.ico`) are served from that CDN. Nuxt resolves public assets against `cdnURL`, falling back to `app.baseURL`. However, a static `app.head` link such as `href: '/favicon.ico'` above is a literal path and is **not** resolved against `cdnURL`. To point the favicon at the resolved location, build the `href` from runtime config with [`useHead()`](/docs/api/composables/use-head) in `app.vue`:
 
 ```vue [app/app.vue]
 <script setup lang="ts">
@@ -48,7 +48,7 @@ useHead({
 ```
 ::
 
-You can also provide any of the keys listed below in [Types](/docs/4.x/getting-started/seo-meta#types).
+You can also provide any of the keys listed below in [Types](/docs/getting-started/seo-meta#types).
 
 ### Default Tags
 
@@ -73,7 +73,7 @@ export default defineNuxtConfig({
 
 ## `useHead`
 
-The [`useHead`](/docs/4.x/api/composables/use-head) composable function supports reactive input, allowing you to manage your head tags programmatically.
+The [`useHead`](/docs/api/composables/use-head) composable function supports reactive input, allowing you to manage your head tags programmatically.
 
 ```vue twoslash [app/app.vue]
 <script setup lang="ts">
@@ -90,11 +90,11 @@ useHead({
 </script>
 ```
 
-We recommend taking a look at the [`useHead`](/docs/4.x/api/composables/use-head) and [`useHeadSafe`](/docs/4.x/api/composables/use-head-safe) composables.
+We recommend taking a look at the [`useHead`](/docs/api/composables/use-head) and [`useHeadSafe`](/docs/api/composables/use-head-safe) composables.
 
 ## `useSeoMeta`
 
-The [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta) composable lets you define your site's SEO meta tags as an object with full type safety.
+The [`useSeoMeta`](/docs/api/composables/use-seo-meta) composable lets you define your site's SEO meta tags as an object with full type safety.
 
 This helps you avoid typos and common mistakes, such as using `name` instead of `property`.
 
@@ -111,11 +111,11 @@ useSeoMeta({
 </script>
 ```
 
-:read-more{to="/docs/4.x/api/composables/use-seo-meta"}
+:read-more{to="/docs/api/composables/use-seo-meta"}
 
 ## Components
 
-While using [`useHead`](/docs/4.x/api/composables/use-head) is recommended in all cases, you may have a personal preference for defining your head tags in your template using components.
+While using [`useHead`](/docs/api/composables/use-head) is recommended in all cases, you may have a personal preference for defining your head tags in your template using components.
 
 Nuxt provides the following components for this purpose: `<Title>`, `<Base>`, `<NoScript>`, `<Style>`, `<Meta>`, `<Link>`, `<Body>`, `<Html>` and `<Head>`. Note
 the capitalization of these components ensuring we don't use invalid native HTML tags.
@@ -147,7 +147,7 @@ const title = ref('Hello World')
 </template>
 ```
 
-It's suggested to wrap your components in either a `<Head>` or `<Html>` components as tags will be deduped more intuitively.
+It's suggested to wrap your components in either a `<Head>` or `<Html>` component as tags will be deduped more intuitively.
 
 ::warning
 If you need to duplicate tags across client-server boundaries, apply a `key` attribute on the `<Head>` component.
@@ -155,7 +155,7 @@ If you need to duplicate tags across client-server boundaries, apply a `key` att
 
 ## Types
 
-Below are the non-reactive types used for [`useHead`](/docs/4.x/api/composables/use-head), [`app.head`](/docs/4.x/api/nuxt-config#head) and components.
+Below are the non-reactive types used for [`useHead`](/docs/api/composables/use-head), [`app.head`](/docs/api/nuxt-config#head) and components.
 
 ```ts [Types]
 interface MetaObject {
@@ -244,7 +244,7 @@ If you want to use a function (for full control), then this cannot be set in you
 
 ::
 
-Now, if you set the title to `My Page` with [`useHead`](/docs/4.x/api/composables/use-head) on another page of your site, the title would appear as 'My Page - Site Title' in the browser tab. You could also pass `null` to default to 'Site Title'.
+Now, if you set the title to `My Page` with [`useHead`](/docs/api/composables/use-head) on another page of your site, the title would appear as 'My Page - Site Title' in the browser tab. You could also pass `null` to default to 'Site Title'.
 
 ### Template Parameters
 
@@ -292,7 +292,7 @@ useHead({
 
 ### With `definePageMeta`
 
-Within your [`app/pages/` directory](/docs/4.x/directory-structure/app/pages), you can use `definePageMeta` along with [`useHead`](/docs/4.x/api/composables/use-head) to set metadata based on the current route.
+Within your [`app/pages/` directory](/docs/directory-structure/app/pages), you can use `definePageMeta` along with [`useHead`](/docs/api/composables/use-head) to set metadata based on the current route.
 
 For example, you can first set the current page title (this is extracted at build time via a macro, so it can't be set dynamically):
 
@@ -316,9 +316,9 @@ useHead({
 </script>
 ```
 
-:link-example{to="/docs/4.x/examples/features/meta-tags"}
+:link-example{to="/docs/examples/features/meta-tags"}
 
-:read-more{to="/docs/4.x/directory-structure/app/pages/#page-metadata"}
+:read-more{to="/docs/directory-structure/app/pages/#page-metadata"}
 
 ### Dynamic Title
 
@@ -351,7 +351,7 @@ useHead({
 
 ### External CSS
 
-The example below shows how you might enable Google Fonts using either the `link` property of the [`useHead`](/docs/4.x/api/composables/use-head) composable or using the `<Link>` component:
+The example below shows how you might enable Google Fonts using either the `link` property of the [`useHead`](/docs/api/composables/use-head) composable or using the `<Link>` component:
 
 ::code-group