@nuxt/docs-nightly 5.0.0-29555264.66acadfc → 5.0.0-29555522.b030db42

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

@@ -348,6 +348,22 @@ If you define redirect route rules, the property name has changed:
 - **Runtime hooks**: `nitroApp.hooks.hook('beforeResponse', ...)` and `nitroApp.hooks.hook('afterResponse', ...)` have been replaced by `nitroApp.hooks.hook('response', ...)`.
 - **`getRouteRules()` from `nitro/app`**: On the server, the Nitro helper changed from `getRouteRules(event)` to `getRouteRules(method, pathname)`, which returns `{ routeRules }`.
 
+### Removal of Legacy `_renderResponse` Support
+
+🚦 **Impact Level**: Minimal
+
+#### What Changed
+
+`ssrContext._renderResponse` is no longer checked as a fallback. Only the internal `ssrContext['~renderResponse']` (set by Nuxt's own router composable) is used.
+
+#### Reasons for Change
+
+The `_renderResponse` property on `ssrContext` was kept as a backward-compatibility fallback after [#33896](https://github.com/nuxt/nuxt/pull/33896) migrated the internal API to `~renderResponse`. The TODO comments indicated it should be removed in Nuxt v5.
+
+#### Migration Steps
+
+If you were setting `ssrContext._renderResponse` directly (which was never a public API), use `ssrContext['~renderResponse']` instead. The Nuxt router composable already uses the new property, so no changes are needed if you're going through `navigateTo` or route middleware.
+
 ### Non-Async `callHook`
 
 🚦 **Impact Level**: Minimal

package/2.directory-structure/1.app/1.layouts.md

@@ -168,7 +168,7 @@ This is useful when you want to manage layouts centrally in your configuration r
 
 :link-example{to="/docs/4.x/examples/features/layouts"}
 
-## Passing Props to Layouts
+## Passing Props to Layouts :badge[+4.4]{color="primary" class="align-middle"}
 
 You can pass props to layouts in several ways.
 

package/4.api/1.components/8.nuxt-island.md

@@ -48,6 +48,10 @@ This is similar to using `v-html` with external content - the remote server can
 The `dangerouslyLoadClientComponents` prop controls an additional layer of risk: whether to also download and execute client components from the remote source. Even with `dangerouslyLoadClientComponents` disabled (the default), you are still trusting the remote server's HTML output.
 ::
 
+::note
+Component props and context are sent as GET query parameters to enable caching. Query parameters may be visible in server access logs, CDN caches, and HTTP `Referer` headers.
+::
+
 ::note
 By default, component islands are scanned from the `~/components/islands/` directory. So the `~/components/islands/MyIsland.vue` component could be rendered with `<NuxtIsland name="MyIsland" />`.
 ::

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "5.0.0-29555264.66acadfc",
+  "version": "5.0.0-29555522.b030db42",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",