@nuxt/docs-nightly 4.6.0-29840992.7ccd5a64 → 4.6.0-29841789.b58e27b1

package/1.getting-started/18.upgrade.md

@@ -103,20 +103,19 @@ On Nuxt 5 the same names are auto-imported from `nuxt/server`, so explicit impor
 | `handleCors(event, options)` returns `true` when it answered a preflight request. | `handleCors(event, options)` returns the preflight `Response` to return from the handler, or `false`. |
 | `readValidatedBody` and `getValidatedQuery` take a validation function. | They take a [Standard Schema](https://standardschema.dev) or a function. |
 | `createError({ statusCode, statusMessage })` | `createError({ status, statusText })` |
-| `useSession` and friends seal an `h3` cookie with the `password` you pass. | They seal a `nuxt-session` cookie, by default with a secret derived from `appSecret`. The two are not interchangeable: a session one issues does not unseal with the other. |
+| h3's `useSession`, `getSession`, `updateSession` and `clearSession` seal an `h3` cookie with the `password` you pass. | They seal a `nuxt-session` cookie, by default with a secret derived from `appSecret`. The two are not interchangeable: a session one issues does not unseal with the other. |
 | `getResponseHeader`, `setResponseHeader`, `appendResponseHeader`, `removeResponseHeader` | `event.res.headers.get()`, `.set()`, `.append()`, `.delete()` |
 | `getMethod(event)`, `getRequestHost(event)` | `event.req.method`, `event.url.host` |
 
 ### Helpers Outside `nuxt/server`
 
-For h3 or Nitro helpers that `nuxt/server` does not provide, such as `readMultipartFormData`, `proxyRequest`, `useStorage` or `defineCachedEventHandler`, pass them `toNuxtRequestEvent(event)`, which is the h3 v1 event on Nuxt 4. Code that does this is tied to the server runtime and needs revisiting on Nuxt 5.
+For a handler that needs h3 or Nitro helpers that `nuxt/server` does not provide, such as `readMultipartFormData`, `proxyRequest`, `useStorage` or `defineCachedEventHandler`, keep importing `defineEventHandler` and those helpers from `h3` (or `nitropack/runtime`) for that handler. Code that does this is tied to the server runtime and needs revisiting on Nuxt 5.
 
 ```ts [server/api/upload.post.ts]
-import { defineEventHandler, toNuxtRequestEvent } from 'nuxt/server'
-import { readMultipartFormData } from 'h3'
+import { defineEventHandler, readMultipartFormData } from 'h3'
 
 export default defineEventHandler(async (event) => {
-  const parts = await readMultipartFormData(toNuxtRequestEvent(event))
+  const parts = await readMultipartFormData(event)
   return { received: parts?.length ?? 0 }
 })
 ```

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`.
 
@@ -87,7 +86,7 @@ export default defineEventHandler(async (event) => {
 })
 ```
 
-`NuxtRequestEvent` is the same request in the shape the configured builder provides, which is h3 v1'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 v1's `H3Event` under `@nuxt/nitro-server`.
 
 ## Validation
 
@@ -157,31 +156,18 @@ The session travels in the cookie, so it is limited to what a browser will accep
 
 `nuxt/server` isn't a re-export of h3, so if you need something else that h3 and Nitro offer, such as the server lifecycle (`defineNitroPlugin`, `defineNitroErrorHandler` and the Nitro app hooks), you would import it directly.
 
-Most of those helpers take the event as it is:
+For a handler that needs h3's own helpers, such as `readRawBody`, `readMultipartFormData`, `assertMethod`, `proxyRequest`, `fetchWithEvent` or `writeEarlyHints`, or that reads `event.node` or `event.waitUntil()`, import `defineEventHandler` from `h3` for that handler:
 
 ```ts [server/api/upload.post.ts]
-import { defineEventHandler, toNuxtRequestEvent } from 'nuxt/server'
-import { readMultipartFormData } from 'h3'
+import { defineEventHandler, readMultipartFormData } from 'h3'
 
 export default defineEventHandler(async (event) => {
-  const parts = await readMultipartFormData(toNuxtRequestEvent(event))
+  const parts = await readMultipartFormData(event)
   return { received: parts?.length ?? 0 }
 })
 ```
 
-Under `@nuxt/nitro-server` the event a handler receives is a view of the h3 v1 event, so `toNuxtRequestEvent(event)` is what h3's own helpers take: `readRawBody`, `readFormData`, `readMultipartFormData`, `assertMethod`, `proxy`, `proxyRequest`, `fetchWithEvent` and `writeEarlyHints`, as well as reading `event.node` or `event.waitUntil()`.
-
-Nitro's own APIs mostly take no event at all: `defineCachedEventHandler()`, `useStorage()`, `useDatabase()` and tasks.
-
-::tip
-If you find you are writing Nitro-specific code, you may simply prefer to import `defineEventHandler` from `h3` instead:
-
-```ts [server/api/proxy.ts]
-import { defineEventHandler, proxyRequest } from 'h3'
-
-export default defineEventHandler(event => proxyRequest(event, 'https://example.com'))
-```
-::
+Nitro's own APIs mostly take no event at all: `defineCachedEventHandler()`, `useStorage()`, `useDatabase()` and tasks. Import them from `nitropack/runtime`.
 
 ## What Isn't Portable
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.6.0-29840992.7ccd5a64",
+  "version": "4.6.0-29841789.b58e27b1",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",