docs/3.api/2.composables/use-runtime-hook.md (1)

16-19: Revert the added space before the parameter list.

The new whitespace between the generic and the opening parenthesis (> () is non-standard for TypeScript snippets and inconsistent with the rest of the docs. Please keep the previous >( formatting.

-function useRuntimeHook<THookName extends keyof RuntimeNuxtHooks> (
+function useRuntimeHook<THookName extends keyof RuntimeNuxtHooks>(

docs/2.guide/3.going-further/4.kit.md (2)

32-34: Align code fence language with file extension.

Block is labelled ts but filename is test.mjs. Prefer matching the fence to the example.

Apply one of:

-```ts [test.mjs]
+```js [test.mjs]

or

-```ts [test.mjs]
+```ts [test.ts]

---

44-51: CJS example: use js fence and consider destructuring.

• Fence is ts but filename is .cjs; use js for clarity.
• Optional: demonstrate named imports with dynamic import.

Apply:

-```ts [test.cjs]
+```js [test.cjs]

Optional tweak inside example:

-  const kit = await import('@nuxt/kit')
+  const { useNuxt } = await import('@nuxt/kit')

docs/2.guide/1.directory-structure/1.app/1.composables.md (1)

65-70: Consider returning or annotating return type.

Example currently returns nothing; returning values (or annotating as () => void) can reduce confusion when copied.

For example:

 export const useFoo = () => {
   const nuxtApp = useNuxtApp()
   const bar = useBar()
+  return { nuxtApp, bar }
 }

docs/2.guide/4.recipes/3.custom-usefetch.md (1)

74-81: Unify typing of custom $fetch in useAPI examples.

First example casts to typeof $fetch, second does not. Prefer consistency; simplest is to drop the cast for readability (the second example already compiles fine in typical Nuxt TS setups).

Apply this diff to the first example:

-  return useFetch(url, {
-    ...options,
-    $fetch: useNuxtApp().$api as typeof $fetch,
-  })
+  return useFetch(url, {
+    ...options,
+    $fetch: useNuxtApp().$api,
+  })

Also applies to: 104-111

docs/1.getting-started/10.data-fetching.md (1)

33-39: Formatting changes look correct; one minor simplification suggestion.

• All trailing commas/spacing are valid and consistent.
• Optional: in the “Refresh data” example, you can simplify the click handler.

Apply this diff to simplify the handler:

-    <button @click="() => refresh()">
+    <button @click="refresh">

Also applies to: 71-77, 97-99, 200-201, 258-259, 307-307, 320-321, 336-337, 409-410, 429-431, 452-455, 470-470, 481-482, 497-497, 514-515, 529-529, 531-542, 570-570, 575-577, 649-652, 704-704, 747-749, 784-785, 796-796, 809-816

docs/2.guide/1.directory-structure/1.app/3.error.md (1)

15-16: Prefer typed props over runtime validator casting

Using a typed props declaration is clearer and avoids awkward casting to Object. Consider one of:

• Generics
• PropType

Example with generics:

-const props = defineProps({
-  error: Object as () => NuxtError,
-})
+const props = defineProps<{ error: NuxtError }>()

Or with PropType:

+import type { PropType } from 'vue'
 const props = defineProps({
-  error: Object as () => NuxtError,
+  error: { type: Object as PropType<NuxtError>, required: true },
 })

docs/1.getting-started/06.styling.md (1)

296-311: Minor consistency nit: quote only when needed

In class-binding examples, you can omit quotes for identifier-safe keys (active) and keep them where required (text-danger) for consistency across snippets.

Example:

-const classObject = reactive({
-  'active': true,
-  'text-danger': false,
-})
+const classObject = reactive({
+  active: true,
+  'text-danger': false,
+})

docs/1.getting-started/14.layers.md (1)

54-55: Optional: Link to giget auth docs for private GitHub sources

Since this snippet uses an auth token, consider adding a link to giget’s auth docs to guide users on supported env vars/token formats for private repos.

docs/1.getting-started/15.prerendering.md (1)

145-148: Optional: Note on auto-imports for prerenderRoutes

Consider adding a brief note that prerenderRoutes is auto-imported by Nuxt in runtime context so no import is required.

docs/2.guide/3.going-further/1.internals.md (1)

39-69: Make the NuxtApp “interface” snippet valid TypeScript (currently invalid).

Several properties are missing types (e.g. vueApp, hooks) and the block mixes literal values with types in an interface, which is not valid TS. Either mark this block as pseudo-code or add minimal types to make it syntactically valid.

Apply this diff to keep the snippet valid while remaining high-level:

-interface NuxtApp {
-  vueApp // the global Vue application: https://vuejs.org/api/application.html#application-api
-
-  versions // an object containing Nuxt and Vue versions
-
-  // These let you call and add runtime NuxtApp hooks
-  // https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/nuxt.ts#L18
-  hooks
-  hook
-  callHook
-
-  // Only accessible on server-side
-  ssrContext: {
-    url
-    req
-    res
-    runtimeConfig
-    noSSR
-  }
-
-  // This will be stringified and passed from server to client
-  payload: {
-    serverRendered: true
-    data: {}
-    state: {}
-  }
-
-  provide: (name: string, value: any) => void
-}
+interface NuxtApp {
+  // the global Vue application: https://vuejs.org/api/application.html#application-api
+  vueApp: unknown
+
+  // an object containing Nuxt and Vue versions
+  versions: { nuxt: string; vue: string } | Record<string, string>
+
+  // These let you call and add runtime NuxtApp hooks
+  // https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/nuxt.ts#L18
+  hooks: unknown
+  hook: (...args: any[]) => Promise<void>
+  callHook: (...args: any[]) => Promise<void>
+
+  // Only accessible on server-side
+  ssrContext?: {
+    url: string
+    req?: unknown
+    res?: unknown
+    runtimeConfig: unknown
+    noSSR?: boolean
+  }
+
+  // This will be stringified and passed from server to client
+  payload: {
+    serverRendered: boolean
+    data: Record<string, unknown>
+    state: Record<string, unknown>
+  }
+
+  provide: (name: string, value: unknown) => void
+}

docs/2.guide/3.going-further/3.modules.md (1)

683-689: Optional: clarify updateTemplates import in the watch hook snippet

If you expect readers to copy-paste, consider showing import { updateTemplates } from '@nuxt/kit' above for completeness.

docs/3.api/2.composables/use-fetch.md (1)

51-66: Guard browser-only APIs in interceptor example

localStorage is browser-only; add a client guard to avoid SSR/runtime issues when the example is used server-side.

   onResponse ({ request, response, options }) {
     // Process the response data
-    localStorage.setItem('token', response._data.token)
+    if (import.meta.client && typeof localStorage !== 'undefined') {
+      localStorage.setItem('token', response._data?.token)
+    }
   },

docs/1.getting-started/12.error-handling.md (1)

93-96: Prefer typed defineProps or PropType for NuxtError

Object as () => NuxtError is not idiomatic and may mislead; use a TS generic or PropType.

-const props = defineProps({
-  error: Object as () => NuxtError,
-})
+const props = defineProps<{ error: NuxtError }>()

Alternatively:

import type { PropType } from 'vue'
const props = defineProps({
  error: Object as PropType<NuxtError>,
})

docs/3.api/3.utils/define-page-meta.md (2)

176-198: Avoid duplicate keys in the same example object.
The snippet shows middleware defined three times. It’s illustrative, but having the same key repeatedly inside one literal can confuse readers. Consider splitting into separate examples or using an ellipsis between alternatives.

---

224-232: Same note about duplicate keys.
layout is set twice in one object (string then false). Consider separate examples to avoid implying both can coexist.

docs/3.api/2.composables/use-nuxt-data.md (1)

53-57: Guard against undefined cached data in default().
posts.value may be undefined; calling .find will throw. Use optional chaining and a sensible fallback.

Apply this diff:

-  default () {
-    // Find the individual post from the cache and set it as the default value.
-    return posts.value.find(post => post.id === route.params.id)
-  },
+  default () {
+    // Find the individual post from the cache and set it as the default value.
+    return posts.value?.find(post => post.id === route.params.id) ?? null
+  },

docs/3.api/2.composables/use-nuxt-app.md (1)

37-40: Unify arrow-parameter style within the page.
Elsewhere in this page single-arg arrows are parenthesised (e.g. (event) => ...). Consider using (name) => here for consistency.

Apply this diff:

-const nuxtApp = useNuxtApp()
-nuxtApp.provide('hello', name => `Hello ${name}!`)
+const nuxtApp = useNuxtApp()
+nuxtApp.provide('hello', (name) => `Hello ${name}!`)

docs/2.guide/1.directory-structure/1.app/1.components.md (1)

309-324: Importing from #components is valid, but optional for NuxtLink.
NuxtLink is globally available; keeping the import is fine if emphasising explicit imports.

docs/2.guide/1.directory-structure/1.app/1.middleware.md (1)

175-178: Small doc caveat suggestion.
Defaulting route = useRoute() is handy outside middleware, but add a one-liner comment warning not to rely on the default within middleware and to pass to explicitly to avoid warnings.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.vue : Use `<script setup lang="ts">` and the composition API when creating Vue components

Learnt from: Tofandel
PR: nuxt/nuxt#0
File: :0-0
Timestamp: 2024-11-11T12:34:22.648Z
Learning: Ensure that AI-generated summaries accurately reflect the key changes in the PR, focusing on notable changes such as the removal of unused imports and variables starting with underscores.

Learnt from: GalacticHypernova
PR: nuxt/nuxt#26468
File: packages/nuxt/src/components/plugins/loader.ts:24-24
Timestamp: 2024-11-05T15:22:54.759Z
Learning: In `packages/nuxt/src/components/plugins/loader.ts`, the references to `resolve` and `distDir` are legacy code from before Nuxt used the new unplugin VFS and will be removed.

Learnt from: Tofandel
PR: nuxt/nuxt#26468
File: packages/nuxt/src/components/runtime/client-delayed-component.ts:62-62
Timestamp: 2024-11-05T20:04:39.622Z
Learning: In Vue components, when typing the `hydrate` prop for hydration strategies like `hydrateOnInteraction`, use `type: null as PropType<Arguments<typeof hydrateOnInteraction>[0]>` to get the type directly from Vue's hydration methods. Also, remember that `HTMLElementEventMap` is not a type but an object; use `keyof HTMLElementEventMap` when defining prop types for events.

Learnt from: huang-julien
PR: nuxt/nuxt#29366
File: packages/nuxt/src/app/components/nuxt-root.vue:16-19
Timestamp: 2024-12-12T12:36:34.871Z
Learning: In `packages/nuxt/src/app/components/nuxt-root.vue`, when optimizing bundle size by conditionally importing components based on route metadata, prefer using inline conditional imports like:

```js
const IsolatedPage = route?.meta?.isolate ? defineAsyncComponent(() => import('#build/isolated-page.mjs')) : null
```

instead of wrapping the import in a computed property or importing the component unconditionally.

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{ts,tsx} : Follow standard TypeScript conventions and best practices

Learnt from: Tofandel
PR: nuxt/nuxt#33192
File: test/nuxt/use-async-data.test.ts:366-373
Timestamp: 2025-09-10T14:42:56.647Z
Learning: In the Nuxt useAsyncData test "should watch params deeply in a non synchronous way", the foo watcher intentionally updates both params.foo and params.locale using locale.value, simulating a scenario where one watcher consolidates multiple reactive values into a shared params object for testing debounced/non-synchronous behavior.

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Write unit tests for core functionality using `vitest`

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/e2e/**/*.{ts,js} : Write end-to-end tests using Playwright and `nuxt/test-utils`