@nuxt/docs 3.17.2 → 3.17.4

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

@@ -48,7 +48,7 @@ disable SSR globally with the `ssr: false` option or leverage hybrid rendering b
 
 ### Server engine
 
-The Nuxt server engine [Nitro](https://nitro.unjs.io) 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/`.
 

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

@@ -21,7 +21,7 @@ Or follow the steps below to set up a new Nuxt project on your computer.
 <!-- markdownlint-disable-next-line MD001 -->
 #### Prerequisites
 
-- **Node.js** - [`18.x`](https://nodejs.org/en) or newer (but we recommend the [active LTS release](https://github.com/nodejs/release#release-schedule))
+- **Node.js** - [`20.x`](https://nodejs.org/en) or newer (but we recommend the [active LTS release](https://github.com/nodejs/release#release-schedule))
 - **Text editor** - There is no IDE requirement, but we recommend [Visual Studio Code](https://code.visualstudio.com/) with the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (previously known as Volar) or [WebStorm](https://www.jetbrains.com/webstorm/), which, along with [other JetBrains IDEs](https://www.jetbrains.com/ides/), offers great Nuxt support right out-of-the-box.
 - **Terminal** - In order to run Nuxt commands
 
@@ -54,6 +54,10 @@ pnpm create nuxt <project-name>
 bun create nuxt <project-name>
 ```
 
+```bash [deno]
+deno -A npm:create-nuxt@latest <project-name>
+```
+
 ::
 
 ::tip
@@ -96,6 +100,10 @@ bun run dev -o
 # To use the Bun runtime during development
 # bun --bun run dev -o
 ```
+
+```bash [deno]
+deno run dev -o
+```
 ::
 
 ::tip{icon="i-lucide-circle-check"}

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

@@ -149,7 +149,7 @@ Nuxt uses [`nuxt.config.ts`](/docs/guide/directory-structure/nuxt-config) file a
 
 Name                                         | Config File               |  How To Configure
 ---------------------------------------------|---------------------------|-------------------------
-[Nitro](https://nitro.unjs.io)               | ~~`nitro.config.ts`~~     | Use [`nitro`](/docs/api/nuxt-config#nitro) 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`
@@ -171,8 +171,8 @@ Name                                         | Config File             | How To
 
 If you need to pass options to `@vitejs/plugin-vue` or `@vitejs/plugin-vue-jsx`, you can do this in your `nuxt.config` file.
 
-- `vite.vue` for `@vitejs/plugin-vue`. Check available options [here](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue).
-- `vite.vueJsx` for `@vitejs/plugin-vue-jsx`. Check available options [here](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue-jsx).
+- `vite.vue` for `@vitejs/plugin-vue`. Check [available options](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue).
+- `vite.vueJsx` for `@vitejs/plugin-vue-jsx`. Check [available options](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue-jsx).
 
 ```ts twoslash [nuxt.config.ts]
 export default defineNuxtConfig({

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

@@ -145,7 +145,7 @@ useHead({
 })
 ```
 
-Nuxt uses `unhead` under the hood, and you can refer to its full documentation [here](https://unhead.unjs.io).
+Nuxt uses `unhead` under the hood, and you can refer to [its full documentation](https://unhead.unjs.io).
 
 ### Modifying The Rendered Head With A Nitro Plugin
 

package/1.getting-started/10.data-fetching.md

@@ -610,7 +610,7 @@ onMounted(() => console.log(document.cookie))
 </script>
 ```
 
-## Options API support
+## Options API Support
 
 Nuxt provides a way to perform `asyncData` fetching within the Options API. You must wrap your component definition within `defineNuxtComponent` for this to work.
 
@@ -744,7 +744,7 @@ const { data } = await useFetch('/api/superjson', {
 
 ## Recipes
 
-### Consuming SSE (Server Sent Events) via POST request
+### Consuming SSE (Server-Sent Events) via POST request
 
 ::tip
 If you're consuming SSE via GET request, you can use [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource) or VueUse composable [`useEventSource`](https://vueuse.org/core/useEventSource/).

package/1.getting-started/15.prerendering.md

@@ -79,7 +79,7 @@ export default defineNuxtConfig({
 
 Setting `nitro.prerender` to `true` is similar to `nitro.prerender.crawlLinks` to `true`.
 
-::read-more{to="https://nitro.unjs.io/config#prerender"}
+::read-more{to="https://nitro.build/config#prerender"}
 Read more about pre-rendering in the Nitro documentation.
 ::
 
@@ -99,7 +99,7 @@ export default defineNuxtConfig({
 });
 ```
 
-::read-more{to="https://nitro.unjs.io/config/#routerules"}
+::read-more{to="https://nitro.build/config/#routerules"}
 Read more about Nitro's `routeRules` configuration.
 ::
 

package/1.getting-started/16.deployment.md

@@ -62,7 +62,7 @@ By default, the workload gets distributed to the workers with the round robin st
 
 ### Learn More
 
-:read-more{to="https://nitro.unjs.io/deploy/node" title="the Nitro documentation for node-server preset"}
+:read-more{to="https://nitro.build/deploy/node" title="the Nitro documentation for node-server preset"}
 
 :video-accordion{title="Watch Daniel Roe's short video on the topic" videoId="0x1H6K5yOfs"}
 
@@ -111,7 +111,7 @@ export default defineNuxtConfig({
 NITRO_PRESET=node-server nuxt build
 ```
 
-🔎 Check [the Nitro deployment](https://nitro.unjs.io/deploy) for all possible deployment presets and providers.
+🔎 Check [the Nitro deployment](https://nitro.build/deploy) for all possible deployment presets and providers.
 
 ## CDN Proxy
 

package/1.getting-started/17.testing.md

@@ -280,7 +280,7 @@ mockNuxtImport('useStorage', () => {
 ```
 
 ::note
-`mockNuxtImport` can only be used once per mocked import per test file. It is actually a macro that gets transformed to `vi.mock` and `vi.mock` is hoisted, as described [here](https://vitest.dev/api/vi.html#vi-mock).
+`mockNuxtImport` can only be used once per mocked import per test file. It is actually a macro that gets transformed to `vi.mock` and `vi.mock` is hoisted, as described [in the Vitest docs](https://vitest.dev/api/vi.html#vi-mock).
 ::
 
 If you need to mock a Nuxt import and provide different implementations between tests, you can do it by creating and exposing your mocks using [`vi.hoisted`](https://vitest.dev/api/vi.html#vi-hoisted), and then use those mocks in `mockNuxtImport`. You then have access to the mocked imports, and can change the implementation between tests. Be careful to [restore mocks](https://vitest.dev/api/mock.html#mockrestore) before or after each test to undo mock state changes between runs.

package/1.getting-started/18.upgrade.md

@@ -35,9 +35,7 @@ bun x nuxi upgrade
 To use the latest Nuxt build and test features before their release, read about the [nightly release channel](/docs/guide/going-further/nightly-release-channel) guide.
 
 ::warning
-The nightly release channel `latest` tag is currently tracking the Nuxt v4 branch, meaning that it is particularly likely to have breaking changes right now - be careful!
-
-You can opt in to the 3.x branch nightly releases with `"nuxt": "npm:nuxt-nightly@3x"`.
+The nightly release channel `latest` tag is currently tracking the Nuxt v4 branch, meaning that it is particularly likely to have breaking changes right now — be careful! You can opt in to the 3.x branch nightly releases with `"nuxt": "npm:nuxt-nightly@3x"`.
 ::
 
 ## Testing Nuxt 4
@@ -659,7 +657,7 @@ These aliases were removed, for greater clarity.
 
 The issue came up when adding `dedupe` as an option to `useAsyncData`, and we removed the boolean values as they ended up being _opposites_.
 
-`refresh({ dedupe: false })` meant 'do not _cancel_ existing requests in favour of this new one'. But passing `dedupe: true` within the options of `useAsyncData` means 'do not make any new requests if there is an existing pending request.' (See [PR](https://github.com/nuxt/nuxt/pull/24564#pullrequestreview-1764584361).)
+`refresh({ dedupe: false })` meant **do not _cancel_ existing requests in favour of this new one**. But passing `dedupe: true` within the options of `useAsyncData` means **do not make any new requests if there is an existing pending request.** (See [PR](https://github.com/nuxt/nuxt/pull/24564#pullrequestreview-1764584361).)
 
 #### Migration Steps
 

package/2.guide/1.concepts/3.rendering.md

@@ -152,7 +152,7 @@ Previously every route/page of a Nuxt application and server must use the same r
 
 Nuxt includes route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route!
 
-Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [Nitro caching layer](https://nitro.unjs.io/guide/cache).
+Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [Nitro caching layer](https://nitro.build/guide/cache).
 
 ```ts twoslash [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -219,7 +219,7 @@ With ESR, the rendering process is pushed to the 'edge' of the network - the CDN
 
 When a request for a page is made, instead of going all the way to the original server, it's intercepted by the nearest edge server. This server generates the HTML for the page and sends it back to the user. This process minimizes the physical distance the data has to travel, **reducing latency and loading the page faster**.
 
-Edge-side rendering is possible thanks to [Nitro](https://nitro.unjs.io), the [server engine](/docs/guide/concepts/server-engine) that powers Nuxt. It offers cross-platform support for Node.js, Deno, Cloudflare Workers, and more.
+Edge-side rendering is possible thanks to [Nitro](https://nitro.build/), the [server engine](/docs/guide/concepts/server-engine) that powers Nuxt. It offers cross-platform support for Node.js, Deno, Cloudflare Workers, and more.
 
 The current platforms where you can leverage ESR are:
 - [Cloudflare Pages](https://pages.cloudflare.com) with zero configuration using the git integration and the `nuxt build` command

package/2.guide/1.concepts/4.server-engine.md

@@ -3,7 +3,7 @@ title: Server Engine
 description: 'Nuxt is powered by a new server engine: Nitro.'
 ---
 
-While building Nuxt, we created a new server engine: [Nitro](https://nitro.unjs.io).
+While building Nuxt, we created a new server engine: [Nitro](https://nitro.build/).
 
 It is shipped with many features:
 

package/2.guide/2.directory-structure/1.composables.md

@@ -109,12 +109,12 @@ export { utils } from './nested/utils.ts'
 export default defineNuxtConfig({
   imports: {
     dirs: [
-      // Scan top-level modules
-      'composables',
-      // ... or scan modules nested one level deep with a specific name and file extension
-      'composables/*/index.{ts,js,mjs,mts}',
-      // ... or scan all modules within given directory
-      'composables/**'
+      // Scan top-level composables
+      '~/composables',
+      // ... or scan composables nested one level deep with a specific name and file extension
+      '~/composables/*/index.{ts,js,mjs,mts}',
+      // ... or scan all composables within given directory
+      '~/composables/**'
     ]
   }
 })

package/2.guide/2.directory-structure/1.pages.md

@@ -299,13 +299,13 @@ Of course, you are welcome to define metadata for your own use throughout your a
 
 #### `alias`
 
-You can define page aliases. They allow you to access the same page from different paths. It can be either a string or an array of strings as defined [here](https://router.vuejs.org/guide/essentials/redirect-and-alias.html#Alias) on vue-router documentation.
+You can define page aliases. They allow you to access the same page from different paths. It can be either a string or an array of strings as defined [in the vue-router documentation](https://router.vuejs.org/guide/essentials/redirect-and-alias.html#Alias).
 
 #### `keepalive`
 
 Nuxt will automatically wrap your page in [the Vue `<KeepAlive>` component](https://vuejs.org/guide/built-ins/keep-alive.html#keepalive) if you set `keepalive: true` in your `definePageMeta`. This might be useful to do, for example, in a parent route that has dynamic child routes, if you want to preserve page state across route changes.
 
-When your goal is to preserve state for parent routes use this syntax: `<NuxtPage keepalive />`. You can also set props to be passed to `<KeepAlive>` (see a full list [here](https://vuejs.org/api/built-in-components.html#keepalive)).
+When your goal is to preserve state for parent routes use this syntax: `<NuxtPage keepalive />`. You can also set props to be passed to `<KeepAlive>` (see [a full list](https://vuejs.org/api/built-in-components.html#keepalive)).
 
 You can set a default value for this property [in your `nuxt.config`](/docs/api/nuxt-config#keepalive).
 
@@ -319,7 +319,7 @@ You can define the layout used to render the route. This can be either false (to
 
 #### `layoutTransition` and `pageTransition`
 
-You can define transition properties for the `<transition>` component that wraps your pages and layouts, or pass `false` to disable the `<transition>` wrapper for that route. You can see a list of options that can be passed [here](https://vuejs.org/api/built-in-components.html#transition) or read [more about how transitions work](https://vuejs.org/guide/built-ins/transition.html#transition).
+You can define transition properties for the `<transition>` component that wraps your pages and layouts, or pass `false` to disable the `<transition>` wrapper for that route. You can see [a list of options that can be passed](https://vuejs.org/api/built-in-components.html#transition) or read [more about how transitions work](https://vuejs.org/guide/built-ins/transition.html#transition).
 
 You can set default values for these properties [in your `nuxt.config`](/docs/api/nuxt-config#layouttransition).
 

package/2.guide/2.directory-structure/1.server.md

@@ -97,7 +97,7 @@ export default defineNitroPlugin((nitroApp) => {
 })
 ```
 
-:read-more{to="https://nitro.unjs.io/guide/plugins" title="Nitro Plugins" target="_blank"}
+:read-more{to="https://nitro.build/guide/plugins" title="Nitro Plugins" target="_blank"}
 
 ## Server Utilities
 
@@ -160,7 +160,7 @@ export default defineEventHandler((event) => {
 })
 ```
 
-::tip{to="https://h3.unjs.io/examples/validate-data#validate-params"}
+::tip{to="https://h3.dev/examples/validate-data#validate-params"}
 Alternatively, use `getValidatedRouterParams` with a schema validator such as Zod for runtime and type safety.
 ::
 
@@ -389,7 +389,7 @@ export default eventHandler((event) => {
 
 ### Nitro Config
 
-You can use `nitro` key in `nuxt.config` to directly set [Nitro configuration](https://nitro.unjs.io/config).
+You can use `nitro` key in `nuxt.config` to directly set [Nitro configuration](https://nitro.build/config).
 
 ::warning
 This is an advanced option. Custom config can affect production deployments, as the configuration interface might change over time when Nitro is upgraded in semver-minor versions of Nuxt.
@@ -397,7 +397,7 @@ This is an advanced option. Custom config can affect production deployments, as
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
-  // https://nitro.unjs.io/config
+  // https://nitro.build/config
   nitro: {}
 })
 ```
@@ -464,7 +464,7 @@ Never combine `next()` callback with a legacy middleware that is `async` or retu
 
 ### Server Storage
 
-Nitro provides a cross-platform [storage layer](https://nitro.unjs.io/guide/storage). In order to configure additional storage mount points, you can use `nitro.storage`, or [server plugins](#server-plugins).
+Nitro provides a cross-platform [storage layer](https://nitro.build/guide/storage). In order to configure additional storage mount points, you can use `nitro.storage`, or [server plugins](#server-plugins).
 
 **Example of adding a Redis storage:**
 
@@ -506,7 +506,7 @@ export default defineEventHandler(async (event) => {
 })
 ```
 
-::read-more{to="https://nitro.unjs.io/guide/storage" target="_blank"}
+::read-more{to="https://nitro.build/guide/storage" target="_blank"}
 Read more about Nitro Storage Layer.
 ::
 

package/2.guide/3.going-further/11.nightly-release-channel.md

@@ -16,9 +16,7 @@ Features that are only available on the nightly release channel are marked with
 ::
 
 ::warning
-The `latest` nightly release channel is currently tracking the Nuxt v4 branch, meaning that it is particularly likely to have breaking changes right now - be careful!
-
-You can opt in to the 3.x branch nightly releases with `"nuxt": "npm:nuxt-nightly@3x"`.
+The `latest` nightly release channel is currently tracking the Nuxt v4 branch, meaning that it is particularly likely to have breaking changes right now — be careful! You can opt in to the 3.x branch nightly releases with `"nuxt": "npm:nuxt-nightly@3x"`.
 ::
 
 ## Opting In

package/2.guide/3.going-further/3.modules.md

@@ -24,7 +24,7 @@ yarn create nuxt -t module my-module
 ```
 
 ```bash [pnpm]
-pnpm create nuxt -- -t module my-module
+pnpm create nuxt -t module my-module
 ```
 
 ```bash [bun]

package/3.api/2.composables/use-nuxt-data.md

@@ -108,5 +108,5 @@ async function addTodo () {
 ## Type
 
 ```ts
-useNuxtData<DataT = any> (key: string): { data: Ref<DataT | null> }
+useNuxtData<DataT = any> (key: string): { data: Ref<DataT | undefined> }
 ```

package/3.api/2.composables/use-request-url.md

@@ -11,9 +11,9 @@ links:
 `useRequestURL` is a helper function that returns an [URL object](https://developer.mozilla.org/en-US/docs/Web/API/URL/URL) working on both server-side and client-side.
 
 ::important
-When utilizing [Hybrid Rendering](/docs/guide/concepts/rendering#hybrid-rendering) with cache strategies, all incoming request headers are dropped when handling the cached responses via the [Nitro caching layer](https://nitro.unjs.io/guide/cache) (meaning `useRequestURL` will return `localhost` for the `host`).
+When utilizing [Hybrid Rendering](/docs/guide/concepts/rendering#hybrid-rendering) with cache strategies, all incoming request headers are dropped when handling the cached responses via the [Nitro caching layer](https://nitro.build/guide/cache) (meaning `useRequestURL` will return `localhost` for the `host`).
 
-You can define the [`cache.varies` option](https://nitro.unjs.io/guide/cache#options) to specify headers that will be considered when caching and serving the responses, such as `host` and `x-forwarded-host` for multi-tenant environments.
+You can define the [`cache.varies` option](https://nitro.build/guide/cache#options) to specify headers that will be considered when caching and serving the responses, such as `host` and `x-forwarded-host` for multi-tenant environments.
 ::
 
 ::code-group

package/3.api/3.utils/navigate-to.md

@@ -17,7 +17,7 @@ Make sure to always use `await` or `return` on result of `navigateTo` when calli
 ::
 
 ::note
-`navigateTo` cannot be used within Nitro routes. To perform a server-side redirect in Nitro routes, use [`sendRedirect`](https://h3.unjs.io/utils/response#sendredirectevent-location-code) instead.
+`navigateTo` cannot be used within Nitro routes. To perform a server-side redirect in Nitro routes, use [`sendRedirect`](https://h3.dev/utils/response#sendredirectevent-location-code) instead.
 ::
 
 ### Within a Vue Component

package/3.api/5.kit/11.nitro.md

@@ -194,7 +194,7 @@ function useNitro (): Nitro
 Add plugin to extend Nitro's runtime behavior.
 
 ::tip
-You can read more about Nitro plugins in the [Nitro documentation](https://nitro.unjs.io/guide/plugins).
+You can read more about Nitro plugins in the [Nitro documentation](https://nitro.build/guide/plugins).
 ::
 
 ### Usage

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

@@ -58,10 +58,10 @@ function extendPages(callback: (pages: NuxtPage[]) => void): void
 
 ## `extendRouteRules`
 
-Nuxt is powered by the [Nitro](https://nitro.unjs.io) server engine. With Nitro, you can incorporate high-level logic directly into your configuration, which is useful for actions like redirects, proxying, caching, and appending headers to routes. This configuration works by associating route patterns with specific route settings.
+Nuxt is powered by the [Nitro](https://nitro.build/) server engine. With Nitro, you can incorporate high-level logic directly into your configuration, which is useful for actions like redirects, proxying, caching, and appending headers to routes. This configuration works by associating route patterns with specific route settings.
 
 ::tip
-You can read more about Nitro route rules in the [Nitro documentation](https://nitro.unjs.io/guide/routing#route-rules).
+You can read more about Nitro route rules in the [Nitro documentation](https://nitro.build/guide/routing#route-rules).
 ::
 
 ::tip{icon="i-lucide-video" to="https://vueschool.io/lessons/adding-route-rules-and-route-middlewares?friend=nuxt" target="_blank"}

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

@@ -90,7 +90,7 @@ Hook                     | Arguments                  | Description
 
 ## Nitro App Hooks (runtime, server-side)
 
-See [Nitro](https://nitro.unjs.io/guide/plugins#available-hooks) for all available hooks.
+See [Nitro](https://nitro.build/guide/plugins#available-hooks) for all available hooks.
 
 Hook                   | Arguments             | Description                          | Types
 -----------------------|-----------------------|--------------------------------------|------------------

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs",
-  "version": "3.17.2",
+  "version": "3.17.4",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",