@nuxt/docs-nightly 5.0.0-29681932.2ad16e09 → 5.0.0-29683228.2900c37b

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

@@ -241,7 +241,7 @@ Read more about `useAsyncData`.
 By default, Nuxt waits until a `refresh` is finished before it can be executed again.
 
 ::note
-If you have not fetched data on the server (for example, with `server: false`), then the data _will not_ be fetched until hydration completes. This means even if you await `useFetch` on client-side, `data` will remain null within `<script setup>`.
+If you have not fetched data on the server (for example, with `server: false`), then the data _will not_ be fetched until hydration completes. This means even if you await `useFetch` on client-side, `data` will remain undefined within `<script setup>`.
 ::
 
 ## Options

package/3.guide/4.modules/5.recipes-advanced.md

@@ -239,5 +239,5 @@ Server routes are also type-checked using `tsconfig.app.json` in addition to `ts
 This is required because Nuxt infers the return types of your server endpoints to provide response types in [`$fetch`](/docs/4.x/api/utils/dollarfetch) and [`useFetch`](/docs/4.x/api/composables/use-fetch).
 
 ::warning
-This can cause issues when using **server-only types** in your route files. For example, if a module creates a server-only virtual file using [`addServerTemplate`](/docs/api/kit/templates#addservertemplate) and you declare types for it in `tsconfig.server.json`, those type declarations will only be available in the server context. When the app context type-checks your server routes, it won't recognize these server-only types and will report errors.  To resolve this, you unfortunately need to declare such types in the app context as well.
+This can cause issues when using **server-only types** in your route files. For example, if a module creates a server-only virtual file using [`addServerTemplate`](/docs/4.x/api/kit/templates#addservertemplate) and you declare types for it in `tsconfig.server.json`, those type declarations will only be available in the server context. When the app context type-checks your server routes, it won't recognize these server-only types and will report errors.  To resolve this, you unfortunately need to declare such types in the app context as well.
 ::

package/4.api/2.composables/use-announcer.md

@@ -14,7 +14,7 @@ This composable is available in Nuxt v4.4.2+.
 
 ## Description
 
-A composable for announcing dynamic content changes to screen readers. Unlike [`useRouteAnnouncer`](/docs/api/composables/use-route-announcer) which automatically announces route changes, `useAnnouncer` gives you manual control over what and when to announce.
+A composable for announcing dynamic content changes to screen readers. Unlike [`useRouteAnnouncer`](/docs/4.x/api/composables/use-route-announcer) which automatically announces route changes, `useAnnouncer` gives you manual control over what and when to announce.
 
 Use this for in-page updates like form validation, async operations, toast notifications, and live content changes.
 

package/4.api/2.composables/use-async-data.md

@@ -251,7 +251,7 @@ type AsyncDataOptions<DataT> = {
   default?: () => DataT | Ref<DataT> | null
   transform?: (input: DataT) => DataT | Promise<DataT>
   pick?: string[]
-  watch?: MultiWatchSources | false
+  watch?: MultiWatchSources
   getCachedData?: (key: string, nuxtApp: NuxtApp, ctx: AsyncDataRequestContext) => DataT | undefined
   timeout?: number
 }

package/4.api/2.composables/use-error.md

@@ -23,10 +23,11 @@ You can use this composable in your components, pages, or plugins to access or r
 ```ts
 interface NuxtError<DataT = unknown> {
   status: number
-  statusText: string
+  statusText?: string
   message: string
   data?: DataT
-  error?: true
+  cause?: unknown
+  fatal: boolean
 }
 
 export const useError: () => Ref<NuxtError | undefined>

package/4.api/2.composables/use-fetch.md

@@ -240,7 +240,7 @@ This only caches data when `experimental.payloadExtraction` in `nuxt.config` is
 - `error`: Request failed
 
 ::note
-If you have not fetched data on the server (for example, with `server: false`), then the data _will not_ be fetched until hydration completes. This means even if you await `useFetch` on client-side, `data` will remain null within `<script setup>`.
+If you have not fetched data on the server (for example, with `server: false`), then the data _will not_ be fetched until hydration completes. This means even if you await `useFetch` on client-side, `data` will remain undefined within `<script setup>`.
 ::
 
 ### Examples

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

@@ -28,7 +28,7 @@ To use `useNuxtData`, ensure that the data-fetching composable (`useFetch`, `use
 
 ## Return Values
 
-- `data`: A reactive reference to the cached data associated with the provided key. If no cached data exists, the value will be `null`. This `Ref` automatically updates if the cached data changes, allowing seamless reactivity in your components.
+- `data`: A reactive reference to the cached data associated with the provided key. If no cached data exists, the value will be `undefined`. This `Ref` automatically updates if the cached data changes, allowing seamless reactivity in your components.
 
 ## Example
 

package/4.api/4.commands/test.md

@@ -14,7 +14,7 @@ npx nuxt test [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [
 ```
 <!--/test-cmd-->
 
-The `test` command runs tests using [`@nuxt/test-utils`](/docs/getting-started/testing). This command sets `process.env.NODE_ENV` to `test` if not already set.
+The `test` command runs tests using [`@nuxt/test-utils`](/docs/4.x/getting-started/testing). This command sets `process.env.NODE_ENV` to `test` if not already set.
 
 ## Arguments
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "5.0.0-29681932.2ad16e09",
+  "version": "5.0.0-29683228.2900c37b",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",