@nuxt/docs-nightly 4.0.0-29144650.ca2dff25 → 4.0.0-29146909.8ec609ca

package/2.guide/3.going-further/1.events.md

@@ -74,7 +74,7 @@ declare module '#app' {
   }
 }
 
-declare module 'nitro/types' {
+declare module 'nitropack/types' {
   interface NitroRuntimeHooks {
     'your-nitro-hook': () => void;
   }

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

@@ -614,7 +614,7 @@ export default defineNuxtModule({
         interface MyModuleNitroRules {
           myModule?: { foo: 'bar' }
         }
-        declare module 'nitro/types' {
+        declare module 'nitropack/types' {
           interface NitroRouteRules extends MyModuleNitroRules {}
           interface NitroRouteConfig extends MyModuleNitroRules {}
         }

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

@@ -98,7 +98,7 @@ The `handler` function should be **side-effect free** to ensure predictable beha
     Which only caches data when `experimental.payloadExtraction` of `nuxt.config` is enabled.
   - `pick`: only pick specified keys in this array from the `handler` function result
   - `watch`: watch reactive sources to auto-refresh
-  - `deep`: return data in a deep ref object. It is `false` by default to return data in a shallow ref object for performance.
+  - `deep`: return data in a deep ref object. It is `false` by default to return data in a shallow ref object, which can improve performance if your data does not need to be deeply reactive.
   - `dedupe`: avoid fetching same key more than once at a time (defaults to `cancel`). Possible options:
     - `cancel` - cancels existing requests when a new one is made
     - `defer` - does not make new requests at all if there is a pending request

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

@@ -132,7 +132,7 @@ All fetch options can be given a `computed` or `ref` value. These will be watche
     Which only caches data when `experimental.payloadExtraction` of `nuxt.config` is enabled.
   - `pick`: only pick specified keys in this array from the `handler` function result
   - `watch`: watch an array of reactive sources and auto-refresh the fetch result when they change. Fetch options and URL are watched by default. You can completely ignore reactive sources by using `watch: false`. Together with `immediate: false`, this allows for a fully-manual `useFetch`. (You can [see an example here](/docs/getting-started/data-fetching#watch) of using `watch`.)
-  - `deep`: return data in a deep ref object. It is `false` by default to return data in a shallow ref object for performance.
+  - `deep`: return data in a deep ref object. It is `false` by default to return data in a shallow ref object, which can improve performance if your data does not need to be deeply reactive.
   - `dedupe`: avoid fetching same key more than once at a time (defaults to `cancel`). Possible options:
     - `cancel` - cancels existing requests when a new one is made
     - `defer` - does not make new requests at all if there is a pending request

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

@@ -117,7 +117,7 @@ export default defineNuxtModule({
 
 ```ts twoslash
 // @errors: 2391
-import type { NitroDevEventHandler } from 'nitro/types'
+import type { NitroDevEventHandler } from 'nitropack/types'
 // ---cut---
 function addDevServerHandler (handler: NitroDevEventHandler): void
 ```