@nuxt/docs-nightly 4.4.7-29652887.e4d5cc70 → 4.5.0-29657113.e77d3dbf

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

@@ -230,6 +230,41 @@ definePageMeta({
 
 :link-example{to="/docs/4.x/examples/routing/pages"}
 
+## Named Views
+
+A single route can render into multiple `<NuxtPage>` outlets in a parent component by giving each outlet a `name` and providing a sibling page file for each name.
+
+Use the `name@view.vue` filename convention to declare a named view alongside the default route file:
+
+```bash [Directory Structure]
+-| pages/
+---| parent/
+-----| child.vue
+-----| child@sidebar.vue
+---| parent.vue
+```
+
+Then render each outlet by name from the parent:
+
+```vue [pages/parent.vue]
+<template>
+  <div>
+    <NuxtPage />
+    <aside>
+      <NuxtPage name="sidebar" />
+    </aside>
+  </div>
+</template>
+```
+
+When the user navigates to `/parent/child`, `child.vue` renders into the default `<NuxtPage />` and `child@sidebar.vue` renders into `<NuxtPage name="sidebar" />`. Outlets without a matching named view are left empty.
+
+::note
+`definePageMeta` is read from the default route file only. Meta declared inside a `name@view.vue` sibling has no effect on the route.
+::
+
+:read-more{title="Named Views" to="https://router.vuejs.org/guide/essentials/named-views.html" target="_blank"}
+
 ## Route Groups
 
 In some cases, you may want to group a set of routes together in a way which doesn't affect file-based routing. For this purpose, you can put files in a folder which is wrapped in parentheses - `(` and `)`.

package/3.guide/6.going-further/1.experimental-features.md

@@ -426,10 +426,17 @@ performance in large projects or on Windows platforms.
 
 You can also set this to `chokidar` to watch all files in your source directory.
 
+Set to `'builder'` to reuse the active builder's own file watcher (for example,
+Vite's `server.watcher`) instead of starting a second one. This reduces the
+number of file watchers active in dev mode and becomes the default when
+`future.compatibilityVersion` is `5`. If the active builder does not implement
+its own watcher (currently webpack and rspack), Nuxt logs a warning and falls
+back to its default selection.
+
 ```ts twoslash [nuxt.config.ts]
 export default defineNuxtConfig({
   experimental: {
-    watcher: 'chokidar-granular', // 'chokidar' or 'parcel' are also options
+    watcher: 'chokidar-granular', // 'chokidar', 'parcel' or 'builder' are also options
   },
 })
 ```
@@ -891,6 +898,26 @@ export default defineNuxtConfig({
 See PR #31379 for implementation details.
 ::
 
+## prefetchPreloadTags
+
+When a `<NuxtLink>` is prefetched and the destination route has [payload extraction](#payloadextraction) enabled (the default for prerendered and cached routes), forward any `<link rel="preload">` hints that the destination set via [`useHead`](/docs/4.x/api/composables/use-head) (or via modules like [`@nuxt/image`](https://image.nuxt.com)'s `<NuxtImg preload>`) into the current document.
+
+The forwarded links are downgraded from `rel="preload"` to `rel="prefetch"` so they don't compete with the current page's critical resources. Only user-defined head tags are forwarded; build-time JS/CSS chunk preloads are already handled separately by the prefetch pipeline.
+
+This flag is off by default because, combined with `prefetchOn: 'visibility'` (the `<NuxtLink>` default), it could trigger a lot of cross-route prefetches at once. Enable it once you are confident the destination preloads are worth forwarding for the links your users typically encounter.
+
+```ts twoslash [nuxt.config.ts]
+export default defineNuxtConfig({
+  experimental: {
+    prefetchPreloadTags: true,
+  },
+})
+```
+
+::read-more{icon="i-simple-icons-github" color="gray" to="https://github.com/nuxt/nuxt/issues/34953" target="_blank"}
+See issue #34953 for motivation.
+::
+
 ## granularCachedData
 
 Whether to call and use the result from `getCachedData` when refreshing data for `useAsyncData` and `useFetch` (whether by `watch`, `refreshNuxtData()`, or a manual `refresh()` call.

package/4.api/1.components/2.nuxt-page.md

@@ -44,7 +44,7 @@ In a typical Vue application, a new page component is mounted **only after** the
 
 ## Props
 
-- `name`: tells `<RouterView>` to render the component with the corresponding name in the matched route record's components option.
+- `name`: tells `<RouterView>` to render the component with the corresponding name in the matched route record's components option. See [Named Views](/docs/4.x/directory-structure/app/pages#named-views) for the `name@view.vue` filename convention.
   - type: `string`
 - `route`: route location that has all of its components resolved.
   - type: `RouteLocationNormalized`

package/4.api/2.composables/use-server-seo-meta.md

@@ -8,20 +8,26 @@ links:
     size: xs
 ---
 
-Just like [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta), `useServerSeoMeta` composable lets you define your site's SEO meta tags as a flat object with full TypeScript support.
+::warning
+`useServerSeoMeta` is deprecated. Wrap [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta) in an `if (import.meta.server)` block instead. The auto-import is removed under `future.compatibilityVersion: 5`.
+::
+
+`useServerSeoMeta` lets you define your site's SEO meta tags as a flat object with full TypeScript support, exactly like [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta), but it only runs server-side and is tree-shaken from the client bundle.
 
 :read-more{to="/docs/4.x/api/composables/use-seo-meta"}
 
-In most instances, the meta doesn't need to be reactive as robots will only scan the initial load. So we recommend using [`useServerSeoMeta`](/docs/4.x/api/composables/use-server-seo-meta) as a performance-focused utility that will not do anything (or return a `head` object) on the client.
+For new code, use the server-only pattern directly:
 
 ```vue [app/app.vue]
 <script setup lang="ts">
-useServerSeoMeta({
-  robots: 'index, follow',
-})
+if (import.meta.server) {
+  useSeoMeta({
+    robots: 'index, follow',
+  })
+}
 </script>
 ```
 
-Parameters are exactly the same as with [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta)
+Parameters are exactly the same as with [`useSeoMeta`](/docs/4.x/api/composables/use-seo-meta).
 
 :read-more{to="/docs/4.x/getting-started/seo-meta"}

package/4.api/6.advanced/2.import-meta.md

@@ -25,6 +25,7 @@ Property | Type | Description
 `import.meta.server` | boolean | True when evaluated on the server side.
 `import.meta.nitro` | boolean | True when evaluated on the server side.
 `import.meta.dev` | boolean | True when running the Nuxt dev server.
+`import.meta.envName` | string | The current Nuxt environment name, including custom values passed via `--envName`.
 `import.meta.test` | boolean | True when running in a test context.
 `import.meta.prerender` | boolean | True when rendering HTML on the server in the prerender stage of your build.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.4.7-29652887.e4d5cc70",
+  "version": "4.5.0-29657113.e77d3dbf",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",