@nuxt/docs-nightly 5.0.0-29841065.3867d5bc → 5.0.0-29841792.9ceeba8c

package/3.guide/6.going-further/5.server-imports.md

@@ -49,7 +49,6 @@ This code can run under `@nuxt/nitro-server` and under `@nuxt/vite-server`, and
 | `getRouteRules` | The [route rules](/docs/guide/concepts/rendering#route-rules) matched for the request. |
 | `useRuntimeConfig` | The server's [runtime configuration](/docs/guide/going-further/runtime-config). |
 | `useAppConfig` | The [app config](/docs/directory-structure/app/app-config), as a copy per request when passed the event. |
-| `toNuxtRequestEvent` | The event in the shape the server runtime provides. |
 
 Types are exported alongside the utilities: `RequestEvent`, `RequestEventContext`, `NuxtRequestEvent`, `EventHandler`, `AppRouteRules`, `ServerRoutes`, `CorsOptions`, `ValidateResult`, `NuxtError`, `NuxtErrorDetails`, `NuxtErrorJSON`, `NuxtErrorLike`, `Session`, `SessionConfig`, `SessionData`, `SessionEvent`, `SessionManager`, `SessionPassword` and `SessionUpdate`.
 
@@ -83,7 +82,7 @@ export default defineEventHandler(async (event) => {
 })
 ```
 
-`NuxtRequestEvent` is the same request in the shape the configured builder provides, which is h3's `H3Event` under `@nuxt/nitro-server`. You can get a type-safe version of the event for the server builder you're using by calling `toNuxtRequestEvent(event)`.
+`NuxtRequestEvent` is the same request in the shape the configured builder provides, which is h3's `H3Event` under `@nuxt/nitro-server`.
 
 ## Validation
 
@@ -167,28 +166,15 @@ export default defineEventHandler(async (event) => {
 
 That works for any h3 helper that only reads the request, such as `readRawBody`, `readFormData`, `readMultipartFormData` and `assertMethod`.
 
-A helper that needs the runtime's own event gets it from `toNuxtRequestEvent`:
-
-```ts [server/api/proxy.ts]
-import { defineEventHandler, toNuxtRequestEvent } from 'nuxt/server'
-import { proxyRequest } from 'nitro/h3'
-
-export default defineEventHandler(event => proxyRequest(toNuxtRequestEvent(event), 'https://example.com'))
-```
-
-Helpers that need you to call `toNuxtRequestEvent` are `proxy`, `proxyRequest`, `fetchWithEvent`, `writeEarlyHints`, and reading `event.node`, `event.waitUntil()` or `event.runtime`. The helper works on every builder, and a cast to `NuxtRequestEvent` is safe even if the runtime's event is web-shaped, as it is under `@nuxt/nitro-server`.
-
-Nitro's own APIs mostly take no event at all: `getRouteRules(method, pathname)`, `serverFetch()`, `defineCachedHandler()`, `useStorage()`, `useDatabase()` and tasks.
-
-::tip
-If you find you are writing Nitro-specific code, you may simply prefer to import `defineEventHandler` from `nitro/h3` instead:
+For a handler that needs the runtime's own event, such as one calling `proxy`, `proxyRequest`, `fetchWithEvent` or `writeEarlyHints`, or reading `event.node`, `event.waitUntil()` or `event.runtime`, import `defineEventHandler` from `nitro/h3` for that handler:
 
 ```ts [server/api/proxy.ts]
 import { defineEventHandler, proxyRequest } from 'nitro/h3'
 
 export default defineEventHandler(event => proxyRequest(event, 'https://example.com'))
 ```
-::
+
+Nitro's own APIs mostly take no event at all: `getRouteRules(method, pathname)`, `serverFetch()`, `defineCachedHandler()`, `useStorage()`, `useDatabase()` and tasks.
 
 ## What Isn't Portable
 

package/3.guide/6.going-further/8.builders.md

@@ -330,7 +330,7 @@ One of the modules in the list is `nuxt/server`, the set of [server imports](/do
 
 By default, `nuxt/server` will resolve to the web-standard implementations Nuxt ships. They're written against the `RequestEvent` shape, and they're what `@nuxt/vite-server` runs on.
 
-Whatever event you pass to a handler must match `RequestEvent`. Register your event's type in the `ServerTypes` registry in `@nuxt/schema`, which is what `NuxtRequestEvent` and `useRequestEvent()` resolve to. If your own event object isn't web-shaped, pass handlers a web-shaped view of it (`toNuxtRequestEvent()` returns one) and put your own event on the `~app` property, so `useRequestEvent()` and the render hooks give app code your event instead.
+Whatever event you pass to a handler must match `RequestEvent`. Register your event's type in the `ServerTypes` registry in `@nuxt/schema`, which is what `NuxtRequestEvent` and `useRequestEvent()` resolve to. If your own event object isn't web-shaped, pass handlers a web-shaped view of it. To give app code your own event instead, set it as `~app` on the event you pass the [renderer](#standing-up-the-ssr-renderer).
 
 If your runtime can implement some of these better than the shipped versions, point Nuxt at your own module:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "5.0.0-29841065.3867d5bc",
+  "version": "5.0.0-29841792.9ceeba8c",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",