@nuxt/docs-nightly 4.0.0-29112167.918f1988 → 4.0.0-29112967.ebff42f8

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

@@ -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/18.upgrade.md

@@ -76,6 +76,7 @@ export default defineNuxtConfig({
   //   spaLoadingTemplateLocation: 'within',
   //   parseErrorData: false,
   //   pendingWhenIdle: true,
+  //   alwaysRunFetchOnKeyChange: true,
   //   defaults: {
   //     useAsyncData: {
   //       deep: true
@@ -755,6 +756,46 @@ export default defineNuxtConfig({
 })
 ```
 
+### Key Change Behavior in `useAsyncData` and `useFetch`
+
+🚦 **Impact Level**: Medium
+
+#### What Changed
+
+When using reactive keys in `useAsyncData` or `useFetch`, Nuxt automatically refetches data when the key changes. When `immediate: false` is set, `useAsyncData` will only fetch data when the key changes if the data has already been fetched once.
+
+Previously, `useFetch` had slightly different behavior. It would always fetch data when the key changed.
+
+Now, `useFetch` and `useAsyncData` behave consistently - by only fetch data when the key changes if the data has already been fetched once.
+
+#### Reasons for Change
+
+This ensures consistent behavior between `useAsyncData` and `useFetch`, and prevents unexpected fetches. If you have set `immediate: false`, then you must call `refresh` or `execute` or data will never be fetched in `useFetch` or `useAsyncData`.
+
+#### Migration Steps
+
+This change should generally improve the expected behavior, but if you were expecting changing the key or options of a non-immediate `useFetch`, you now will need to trigger it manually the first time.
+
+```diff
+  const id = ref('123')
+  const { data, execute } = await useFetch('/api/test', {
+    query: { id },
+    immediate: false
+  )
++ watch(id, execute, { once: true })
+```
+
+To opt out of this behavior:
+
+```ts
+// Or globally in your Nuxt config
+export default defineNuxtConfig({
+  experimental: {
+    alwaysRunFetchOnKeyChange: true
+  }
+})
+```
+
 ### Shallow Data Reactivity in `useAsyncData` and `useFetch`
 
 🚦 **Impact Level**: Minimal

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

@@ -0,0 +1,82 @@
+---
+title: "Events"
+description: "Nuxt provides a powerful event system powered by hookable."
+---
+
+# Events
+
+Using events is a great way to decouple your application and allow for more flexible and modular communication between different parts of your code. Events can have multiple listeners that do not depend on each other. For example, you may wish to send an email to your user each time an order has shipped. Instead of coupling your order processing code to your email code, you can emit an event which a listener can receive and use to dispatch an email.
+
+The Nuxt event system is powered by [unjs/hookable](https://github.com/unjs/hookable), which is the same library that powers the Nuxt hooks system.
+
+## Creating Events and Listeners
+
+You can create your own custom events using the `hook` method:
+
+```ts
+const nuxtApp = useNuxtApp()
+
+nuxtApp.hook('app:user:registered', payload => {
+  console.log('A new user has registered!', payload)
+})
+```
+
+To emit an event and notify any listeners, use `callHook`:
+
+```ts
+const nuxtApp = useNuxtApp()
+
+await nuxtApp.callHook('app:user:registered', {
+  id: 1,
+  name: 'John Doe',
+})
+```
+
+You can also use the payload object to enable two-way communication between the emitter and listeners. Since the payload is passed by reference, a listener can modify it to send data back to the emitter.
+
+```ts
+const nuxtApp = useNuxtApp()
+
+nuxtApp.hook('app:user:registered', payload => {
+  payload.message = 'Welcome to our app!'
+})
+
+const payload = {
+  id: 1,
+  name: 'John Doe',
+}
+
+await nuxtApp.callHook('app:user:registered', {
+  id: 1,
+  name: 'John Doe',
+})
+
+// payload.message will be 'Welcome to our app!'
+```
+
+::tip
+You can inspect all events using the **Nuxt DevTools** Hooks panel.
+::
+
+## Augmenting Types
+
+You can augment the types of hooks provided by Nuxt.
+
+```ts
+import { HookResult } from "@nuxt/schema";
+
+declare module '#app' {
+  interface RuntimeNuxtHooks {
+    'your-nuxt-runtime-hook': () => HookResult
+  }
+  interface NuxtHooks {
+    'your-nuxt-hook': () => HookResult
+  }
+}
+
+declare module 'nitro/types' {
+  interface NitroRuntimeHooks {
+    'your-nitro-hook': () => void;
+  }
+}
+```

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

@@ -76,23 +76,4 @@ Learn more about available Nitro lifecycle hooks.
 
 ## Additional Hooks
 
-You can add additional hooks by augmenting the types provided by Nuxt. This can be useful for modules.
-
-```ts
-import { HookResult } from "@nuxt/schema";
-
-declare module '#app' {
-  interface RuntimeNuxtHooks {
-    'your-nuxt-runtime-hook': () => HookResult
-  }
-  interface NuxtHooks {
-    'your-nuxt-hook': () => HookResult
-  }
-}
-
-declare module 'nitro/types' {
-  interface NitroRuntimeHooks {
-    'your-nitro-hook': () => void;
-  }
-}
-```
+Learn more about creating custom hooks in the [Events section](/docs/guide/going-further/events).

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.0.0-29112167.918f1988",
+  "version": "4.0.0-29112967.ebff42f8",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",