@nuxt/docs-nightly 4.6.0-29840865.55e61d75 → 4.6.0-29840992.7ccd5a64

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

@@ -108,9 +108,7 @@ Well done! A browser window should automatically open for <http://localhost:3000
 ::
 
 ::tip{icon="i-lucide-container"}
-If you're using Docker or want a consistent development environment across machines, consider using a dev container.
-
-[Learn more about dev containers](/docs/guide/best-practices/devcontainers)
+If you're using Docker or want a consistent development environment across machines, consider using a dev container. [Learn more about dev containers.](/docs/guide/best-practices/devcontainers)
 ::
 
 ::

package/1.getting-started/15.prerendering.md

@@ -44,7 +44,7 @@ Static and prerender builds also emit `200.html` and `404.html` SPA fallbacks. S
 
 How the Nitro crawler works:
 
-1. Load the HTML of your application's root route (`/`), any non-dynamic pages in your `~/pages` directory, and any other routes in the `nitro.prerender.routes` array.
+1. Load the HTML of your application's root route (`/`), any non-dynamic pages in your `~/pages` directory, and any other routes in the `prerender.routes` array.
 2. Save the HTML and `_payload.json` to the `~/.output/public/` directory to be served statically.
 3. Find all anchor tags (`<a href="...">`) in the HTML to navigate to other routes.
 4. Repeat steps 1-3 for each anchor tag found until there are no more anchor tags to crawl.
@@ -57,16 +57,13 @@ Read more about the `nuxt generate` command.
 
 ### Selective Pre-rendering
 
-You can manually specify routes that [Nitro](/docs/guide/concepts/server-engine) will fetch and pre-render during the build or ignore routes that you don't want to pre-render like `/dynamic` in the `nuxt.config` file:
+You can manually specify routes that Nuxt will fetch and pre-render during the build or ignore routes that you don't want to pre-render like `/dynamic` in the `nuxt.config` file:
 
 ```ts twoslash [nuxt.config.ts]
-// @errors: 2353
 export default defineNuxtConfig({
-  nitro: {
-    prerender: {
-      routes: ['/user/1', '/user/2'],
-      ignore: ['/dynamic'],
-    },
+  prerender: {
+    routes: ['/user/1', '/user/2'],
+    ignore: ['/dynamic'],
   },
 })
 ```
@@ -74,18 +71,15 @@ export default defineNuxtConfig({
 You can combine this with the `crawlLinks` option to pre-render a set of routes that the crawler can't discover like your `/sitemap.xml` or `/robots.txt`:
 
 ```ts twoslash [nuxt.config.ts]
-// @errors: 2353
 export default defineNuxtConfig({
-  nitro: {
-    prerender: {
-      crawlLinks: true,
-      routes: ['/sitemap.xml', '/robots.txt'],
-    },
+  prerender: {
+    crawlLinks: true,
+    routes: ['/sitemap.xml', '/robots.txt'],
   },
 })
 ```
 
-Setting `nitro.prerender` to `true` is similar to `nitro.prerender.crawlLinks` to `true`.
+The top-level `prerender` option applies whichever `server.builder` you use. Builder-specific options, such as Nitro's `concurrency` or `failOnError`, can be set in `nitro.prerender`.
 
 ::read-more{to="https://nitro.build/config#prerender"}
 Read more about pre-rendering in the Nitro documentation.

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

@@ -16,7 +16,7 @@ Pages are Vue components and can have any [valid extension](/docs/api/nuxt-confi
 Nuxt will automatically create a route for every page in your `~/pages/` directory.
 
 ::tip
-Pages are only automatically registered for prerendering if you have not disabled `nitro.prerender.crawlLinks` and you have at least one page in your `nitro.prerender.routes` list. See the [prerendering guide](/docs/getting-started/prerendering).
+Pages are only automatically registered for prerendering if you have not disabled `prerender.crawlLinks` and you have at least one page in your `prerender.routes` list. See the [prerendering guide](/docs/getting-started/prerendering).
 ::
 
 ::code-group

package/2.directory-structure/3.tsconfig.md

@@ -76,5 +76,5 @@ Most `compilerOptions` set in `typescript.tsConfig` are shared with every contex
 ::
 
 ::note
-`typescript.serverTsConfig` and `nitro.typescript.tsConfig` both extend `tsconfig.server.json` and are kept in sync, so setting either has the same effect. Prefer `typescript.serverTsConfig` to keep all four contexts in one place.
+`typescript.serverTsConfig` extends `tsconfig.server.json`. `nitro.typescript.tsConfig` is kept in sync with it but is deprecated, so set `typescript.serverTsConfig` instead.
 ::

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

@@ -278,6 +278,24 @@ export default defineNuxtConfig({
 })
 ```
 
+## serverPathFallback
+
+Loads a client-side navigation that matches no page route as a full document, so the server can respond with a file in `public/`, a server route, or its 404 page. With this enabled, `<NuxtLink to="/brochure.pdf">` and `<NuxtLink to="/rss.xml">` work on click as they do on a hard load.
+
+A path is never reloaded if the current document was already served for it, so hosts that respond to unknown paths with an SPA fallback render the client-side 404 page.
+
+This flag is enabled by default, but you can disable it:
+
+```ts twoslash [nuxt.config.ts]
+export default defineNuxtConfig({
+  experimental: {
+    serverPathFallback: false,
+  },
+})
+```
+
+The option has no effect when `hashMode` is enabled.
+
 ## early404
 
 Responds with an early 404 error for requests whose path cannot match any page route, without loading the Vue app, its plugins or middleware on the server.

package/4.api/6.nuxt-config.md

@@ -116,13 +116,11 @@ NUXT_APP_BASE_URL=./ npm run generate
 ```
 
 ```ts
-// Option 2: Nitro runtime config
+// Option 2: Runtime config
 export default defineNuxtConfig({
-  nitro: {
-    runtimeConfig: {
-      app: {
-        baseURL: './',
-      },
+  runtimeConfig: {
+    app: {
+      baseURL: './',
     },
   },
 })

package/package.json

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