@nuxt/docs-nightly 4.5.1-29752449.30d24817 → 4.5.2-2610052030-052d82e

package/1.getting-started/12.error-handling.md

@@ -8,7 +8,7 @@ Nuxt is a full-stack framework, which means there are several sources of unpreve
 
 - Errors during the Vue rendering lifecycle (SSR & CSR)
 - Server and client startup errors (SSR + CSR)
-- Errors during Nitro server lifecycle ([`server/`](/docs/4.x/directory-structure/server) directory)
+- Errors during Nitro server lifecycle ([`server/`](/docs/directory-structure/server) directory)
 - Errors downloading JS chunks
 
 ::tip
@@ -19,7 +19,7 @@ Nuxt is a full-stack framework, which means there are several sources of unpreve
 
 You can hook into Vue errors using [`onErrorCaptured`](https://vuejs.org/api/composition-api-lifecycle#onerrorcaptured).
 
-In addition, Nuxt provides a [`vue:error`](/docs/4.x/api/advanced/hooks#app-hooks-runtime) hook that will be called if any errors propagate up to the top level.
+In addition, Nuxt provides a [`vue:error`](/docs/api/advanced/hooks#app-hooks-runtime) hook that will be called if any errors propagate up to the top level.
 
 If you are using an error reporting framework, you can provide a global handler through [`vueApp.config.errorHandler`](https://vuejs.org/api/application#app-config-errorhandler). It will receive all Vue errors, even if they are handled.
 
@@ -45,7 +45,7 @@ Note that the `vue:error` hook is based on [`onErrorCaptured`](https://vuejs.org
 Nuxt will call the `app:error` hook if there are any errors in starting your Nuxt application.
 
 This includes:
-- running [Nuxt plugins](/docs/4.x/directory-structure/app/plugins)
+- running [Nuxt plugins](/docs/directory-structure/app/plugins)
 - processing `app:created` and `app:beforeMount` hooks
 - rendering your Vue app to HTML (during SSR)
 - mounting the app (on client-side), though you should handle this case with `onErrorCaptured` or with `vue:error`
@@ -53,18 +53,18 @@ This includes:
 
 ## Nitro Server Errors
 
-You cannot currently define a server-side handler for these errors, but can render an error page, see the [Render an Error Page](/docs/4.x/getting-started/error-handling#error-page) section.
+You cannot currently define a server-side handler for these errors, but can render an error page, see the [Render an Error Page](/docs/getting-started/error-handling#error-page) section.
 
 ## Errors with JS Chunks
 
 You might encounter chunk loading errors due to a network connectivity failure or a new deployment (which invalidates your old, hashed JS chunk URLs). Nuxt provides built-in support for handling chunk loading errors by performing a hard reload when a chunk fails to load during route navigation.
 
-You can change this behavior by setting `experimental.emitRouteChunkError` to `false` (to disable hooking into these errors at all) or to `manual` if you want to handle them yourself. If you want to handle chunk loading errors manually, you can check out the [the automatic implementation](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/plugins/chunk-reload.client.ts) for ideas.
+You can change this behavior by setting `experimental.emitRouteChunkError` to `false` (to disable hooking into these errors at all) or to `manual` if you want to handle them yourself. If you want to handle chunk loading errors manually, you can check out the [automatic implementation](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/plugins/chunk-reload.client.ts) for ideas.
 
 ## Error Page
 
 ::note
-When Nuxt encounters a fatal error (any unhandled error on the server, or an error created with `fatal: true` on the client) it will either render a JSON response (if requested with `Accept: application/json` header) or trigger a full-screen error page.
+When Nuxt encounters a fatal error (any unhandled error on the server, or an error created with `fatal: true` on the client) it will either render a JSON response (if requested with `Accept: application/json` header) or trigger a full-screen error page. With `future.compatibilityVersion: 5`, a page error always triggers the error page, and an error thrown in a server route or server middleware returns a JSON response.
 ::
 
 An error may occur during the server lifecycle when:
@@ -78,7 +78,7 @@ It can also occur on the client side when:
 - mounting your app if the error was not handled with `onErrorCaptured` or `vue:error` hook
 - the Vue app is initialized and mounted in browser (`app:mounted`).
 
-::read-more{to="/docs/4.x/api/advanced/hooks"}
+::read-more{to="/docs/api/advanced/hooks"}
 Discover all the Nuxt lifecycle hooks.
 ::
 
@@ -107,7 +107,7 @@ const handleError = () => clearError({ redirect: '/' })
 </template>
 ```
 
-::read-more{to="/docs/4.x/directory-structure/app/error"}
+::read-more{to="/docs/directory-structure/app/error"}
 Read more about `error.vue` and its uses.
 ::
 
@@ -121,14 +121,14 @@ export default defineNuxtPlugin((nuxtApp) => {
 })
 ```
 
-When you are ready to remove the error page, you can call the [`clearError`](/docs/4.x/api/utils/clear-error) helper function, which takes an optional path to redirect to (for example, if you want to navigate to a 'safe' page).
+When you are ready to remove the error page, you can call the [`clearError`](/docs/api/utils/clear-error) helper function, which takes an optional path to redirect to (for example, if you want to navigate to a 'safe' page).
 
 ::important
 Make sure to check before using anything dependent on Nuxt plugins, such as `$route` or `useRouter`, as if a plugin threw an error, then it won't be re-run until you clear the error.
 ::
 
 ::note
-Rendering an error page is an entirely separate page load, meaning any registered middleware will run again. You can use [`useError`](/docs/4.x/getting-started/error-handling#useerror) in middleware to check if an error is being handled.
+Rendering an error page is an entirely separate page load, meaning any registered middleware will run again. You can use [`useError`](/docs/getting-started/error-handling#useerror) in middleware to check if an error is being handled.
 ::
 
 ::note
@@ -145,7 +145,7 @@ function useError (): Ref<Error | { url, status, statusText, message, descriptio
 
 This function will return the global Nuxt error that is being handled.
 
-::read-more{to="/docs/4.x/api/composables/use-error"}
+::read-more{to="/docs/api/composables/use-error"}
 Read more about `useError` composable.
 ::
 
@@ -158,9 +158,11 @@ function createError (err: string | { cause, data, message, name, stack, status,
 Create an error object with additional metadata. You can pass a string to be set as the error `message` or an object containing error properties. It is usable in both the Vue and Server portions of your app, and is meant to be thrown.
 
 If you throw an error created with `createError`:
-- on server-side, it will trigger a full-screen error page which you can clear with [`clearError`](/docs/4.x/getting-started/error-handling#clearerror).
+- on server-side, it will trigger a full-screen error page which you can clear with [`clearError`](/docs/getting-started/error-handling#clearerror).
 - on client-side, it will throw a non-fatal error for you to handle. If you need to trigger a full-screen error page, then you can do this by setting `fatal: true`.
 
+In development, an error `cause` is preserved and exposed to your error page so you can trace the original error; in production, causes are never included in error responses or the error page payload.
+
 ```vue twoslash [pages/movies/[slug\\].vue]
 <script setup lang="ts">
 const route = useRoute()
@@ -181,7 +183,7 @@ The `statusText` property is intended for short, HTTP-compliant status texts (e.
 For any detailed descriptions, multi-line messages, or content with non-ASCII characters, you should always use the `message` property instead.
 ::
 
-::read-more{to="/docs/4.x/api/utils/create-error"}
+::read-more{to="/docs/api/utils/create-error"}
 Read more about `createError` util.
 ::
 
@@ -191,11 +193,11 @@ Read more about `createError` util.
 function showError (err: string | Error | { status, statusText }): Error
 ```
 
-You can call this function at any point on client-side, or (on server side) directly within middleware, plugins or `setup()` functions. It will trigger a full-screen error page which you can clear with [`clearError`](/docs/4.x/getting-started/error-handling#clearerror).
+You can call this function at any point on client-side, or (on server side) directly within middleware, plugins or `setup()` functions. It will trigger a full-screen error page which you can clear with [`clearError`](/docs/getting-started/error-handling#clearerror).
 
 It is recommended instead to use `throw createError()`.
 
-::read-more{to="/docs/4.x/api/utils/show-error"}
+::read-more{to="/docs/api/utils/show-error"}
 Read more about `showError` util.
 ::
 
@@ -207,13 +209,13 @@ function clearError (options?: { redirect?: string }): Promise<void>
 
 This function will clear the currently handled Nuxt error. It also takes an optional path to redirect to (for example, if you want to navigate to a 'safe' page).
 
-::read-more{to="/docs/4.x/api/utils/clear-error"}
+::read-more{to="/docs/api/utils/clear-error"}
 Read more about `clearError` util.
 ::
 
 ## Render Error in Component
 
-Nuxt also provides a [`<NuxtErrorBoundary>`](/docs/4.x/api/components/nuxt-error-boundary) component that allows you to handle client-side errors within your app, without replacing your entire site with an error page.
+Nuxt also provides a [`<NuxtErrorBoundary>`](/docs/api/components/nuxt-error-boundary) component that allows you to handle client-side errors within your app, without replacing your entire site with an error page.
 
 This component is responsible for handling errors that occur within its default slot. On client-side, it will prevent the error from bubbling up to the top level, and will render the `#error` slot instead.
 
@@ -238,4 +240,4 @@ If you navigate to another route, the error will be cleared automatically.
 </template>
 ```
 
-:link-example{to="/docs/4.x/examples/advanced/error-handling"}
+:link-example{to="/docs/examples/advanced/error-handling"}

package/1.getting-started/13.server.md

@@ -4,7 +4,7 @@ description: Build full-stack applications with Nuxt's server framework. You can
 navigation.icon: i-lucide-pc-case
 ---
 
-:read-more{to="/docs/4.x/directory-structure/server"}
+:read-more{to="/docs/directory-structure/server"}
 
 ## Powered by Nitro
 
@@ -38,7 +38,7 @@ And you can directly return `text`, `json`, `html` or even a `stream`.
 
 Out-of-the-box, it supports **hot module replacement** and **auto-import** like the other parts of your Nuxt application.
 
-:read-more{to="/docs/4.x/directory-structure/server"}
+:read-more{to="/docs/directory-structure/server"}
 
 ## Universal Deployment
 
@@ -59,11 +59,11 @@ Or for other runtimes:
   :card{icon="i-logos-bun" title="Bun" to="https://bun.com" target="_blank"}
 ::
 
-:read-more{to="/docs/4.x/getting-started/deployment"}
+:read-more{to="/docs/getting-started/deployment"}
 
 ## Hybrid Rendering
 
-Nitro has a powerful feature called `routeRules` which allows you to define a set of rules to customize how each route of your Nuxt app is rendered (and more).
+Nuxt has a powerful feature called `routeRules` which allows you to define a set of rules to customize how each route of your Nuxt app is rendered (and more). Nuxt compiles the rules, and the default server builder (Nitro) applies the server-side ones.
 
 ```ts twoslash [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -81,8 +81,8 @@ export default defineNuxtConfig({
 })
 ```
 
-::read-more{to="/docs/4.x/guide/concepts/rendering#hybrid-rendering"}
-Learn about all available route rules are available to customize the rendering mode of your routes.
+::read-more{to="/docs/guide/concepts/rendering#hybrid-rendering"}
+Learn about all the route rules available to customize the rendering mode of your routes.
 ::
 
 In addition, there are some route rules (for example, `ssr`, `appMiddleware`, and `noScripts`) that are Nuxt specific to change the behavior when rendering your pages to HTML.
@@ -91,4 +91,4 @@ Some route rules (`appMiddleware`, `redirect` and `prerender`) also affect clien
 
 Nitro is used to build the app for server side rendering, as well as pre-rendering.
 
-:read-more{to="/docs/4.x/guide/concepts/rendering"}
+:read-more{to="/docs/guide/concepts/rendering"}

package/1.getting-started/14.layers.md

@@ -9,8 +9,8 @@ One of the core features of Nuxt is the layers and extending support. You can ex
 ## Use Cases
 
 - Share reusable configuration presets across projects using `nuxt.config` and `app.config`
-- Create a component library using [`app/components/`](/docs/4.x/directory-structure/app/components) directory
-- Create utility and composable library using [`app/composables/`](/docs/4.x/directory-structure/app/composables) and [`app/utils/`](/docs/4.x/directory-structure/app/utils) directories
+- Create a component library using [`app/components/`](/docs/directory-structure/app/components) directory
+- Create utility and composable library using [`app/composables/`](/docs/directory-structure/app/composables) and [`app/utils/`](/docs/directory-structure/app/utils) directories
 - Create Nuxt module presets
 - Share standard setup across projects
 - Create Nuxt themes
@@ -30,7 +30,7 @@ In addition, named layer aliases to the `srcDir` of each of these layers will au
 Named layer aliases were introduced in Nuxt v3.16.0.
 ::
 
-In addition, you can extend from a layer by adding the [extends](/docs/4.x/api/nuxt-config#extends) property to your [`nuxt.config`](/docs/4.x/directory-structure/nuxt-config) file.
+In addition, you can extend from a layer by adding the [extends](/docs/api/nuxt-config#extends) property to your [`nuxt.config`](/docs/directory-structure/nuxt-config) file.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -127,7 +127,7 @@ layers/
 This pattern is useful for creating base layers with defaults that can be progressively overridden by more specific layers.
 ::
 
-Alternatively, you can control the order of your `~~/layers` directories from `nuxt.config` by referencing them in [`extends`](/docs/4.x/api/nuxt-config#extends), without renaming your directories. The entries are ordered like any other `extends` layer, with the **first entry having the highest priority**:
+Alternatively, you can control the order of your `~~/layers` directories from `nuxt.config` by referencing them in [`extends`](/docs/api/nuxt-config#extends), without renaming your directories. The entries are ordered like any other `extends` layer, with the **first entry having the highest priority**:
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -165,11 +165,11 @@ If you also have `~~/layers/custom`, the priority order is:
 - `@my-themes/awesome`
 - `github:my-themes/awesome#v1` (lowest)
 
-::read-more{to="/docs/4.x/directory-structure/layers"}
+::read-more{to="/docs/directory-structure/layers"}
 Learn about the **layers/ directory** to organize and share reusable code, components, composables, and configurations across your Nuxt application.
 ::
 
-::read-more{to="/docs/4.x/guide/going-further/layers"}
+::read-more{to="/docs/guide/going-further/layers"}
 Read more about layers in the **Layer Author Guide**.
 ::
 

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

@@ -6,11 +6,11 @@ navigation.icon: i-lucide-file-code-2
 
 Nuxt allows for select pages from your application to be rendered at build time. Nuxt will serve the prebuilt pages when requested instead of generating them on the fly.
 
-:read-more{title="Nuxt rendering modes" to="/docs/4.x/guide/concepts/rendering"}
+:read-more{title="Nuxt rendering modes" to="/docs/guide/concepts/rendering"}
 
 ## Crawl-based Pre-rendering
 
-Use the [`nuxt generate` command](/docs/4.x/api/commands/generate) to build and pre-render your application using the [Nitro](/docs/4.x/guide/concepts/server-engine) crawler. This command is similar to `nuxt build` with the `nitro.static` option set to `true`, or running `nuxt build --prerender`.
+Use the [`nuxt generate` command](/docs/api/commands/generate) to build and pre-render your application using the [Nitro](/docs/guide/concepts/server-engine) crawler. This command is similar to `nuxt build` with the `nitro.static` option set to `true`, or running `nuxt build --prerender`.
 
 This will build your site, stand up a nuxt instance, and, by default, prerender the root page `/` along with any of your site's pages it links to, any of your site's pages they link to, and so on.
 
@@ -40,33 +40,30 @@ deno x nuxt generate
 
 You can now deploy the `.output/public` directory to any static hosting service or preview it locally with `npx serve .output/public`.
 
-Static and prerender builds also emit `200.html` and `404.html` SPA fallbacks. See [What are 200.html and 404.html?](/docs/4.x/guide/concepts/rendering#what-are-200html-and-404html).
+Static and prerender builds also emit `200.html` and `404.html` SPA fallbacks. See [What are 200.html and 404.html?](/docs/guide/concepts/rendering#what-are-200html-and-404html).
 
-Working of the Nitro crawler:
+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.
 
 This is important to understand since pages that are not linked to a discoverable page can't be pre-rendered automatically.
 
-::read-more{to="/docs/4.x/api/commands/generate#nuxt-generate"}
+::read-more{to="/docs/api/commands/generate#nuxt-generate"}
 Read more about the `nuxt generate` command.
 ::
 
 ### Selective Pre-rendering
 
-You can manually specify routes that [Nitro](/docs/4.x/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.
@@ -111,9 +105,9 @@ export default defineNuxtConfig({
 Read more about Nitro's `routeRules` configuration.
 ::
 
-As a shorthand, you can also configure this in a page file using [`defineRouteRules`](/docs/4.x/api/utils/define-route-rules).
+As a shorthand, you can also configure this in a page file using [`defineRouteRules`](/docs/api/utils/define-route-rules).
 
-::read-more{to="/docs/4.x/guide/going-further/experimental-features#inlinerouterules" icon="i-lucide-star"}
+::read-more{to="/docs/guide/going-further/experimental-features#inlinerouterules" icon="i-lucide-star"}
 This feature is experimental and in order to use it you must enable the `experimental.inlineRouteRules` option in your `nuxt.config`.
 ::
 
@@ -145,14 +139,14 @@ export default defineNuxtConfig({
 
 ## Payload Extraction
 
-When Nuxt renders a page on the server, it serializes the results of your data fetching ([`useAsyncData`](/docs/4.x/api/composables/use-async-data) and [`useFetch`](/docs/4.x/api/composables/use-fetch)) and app state ([`useState`](/docs/4.x/api/composables/use-state)) into a payload so the client can hydrate without re-fetching. With payload extraction enabled, Nuxt also writes this payload to a `_payload.json` file alongside the route's HTML:
+When Nuxt renders a page on the server, it serializes the results of your data fetching ([`useAsyncData`](/docs/api/composables/use-async-data) and [`useFetch`](/docs/api/composables/use-fetch)) and app state ([`useState`](/docs/api/composables/use-state)) into a payload so the client can hydrate without re-fetching. With payload extraction enabled, Nuxt also writes this payload to a `_payload.json` file alongside the route's HTML:
 
 - Prerendered routes generate their payload file at build time.
-- Routes using [ISR or SWR caching](/docs/4.x/guide/concepts/rendering#hybrid-rendering) generate their payload file when the route is first rendered, even on a hybrid (non-static) site.
+- Routes using [ISR or SWR caching](/docs/guide/concepts/rendering#hybrid-rendering) generate their payload file when the route is first rendered, even on a hybrid (non-static) site.
 
 During client-side navigation, Nuxt fetches the `_payload.json` file for the destination route and reuses the extracted data instead of running the data fetching again in the browser.
 
-You can control this behavior with the [`experimental.payloadExtraction`](/docs/4.x/api/nuxt-config#payloadextraction) option:
+You can control this behavior with the [`experimental.payloadExtraction`](/docs/api/nuxt-config#payloadextraction) option:
 
 - `'client'` - The payload is inlined in the HTML for the initial render and extracted to `_payload.json` files for client-side navigation. There is no extra network request on first load.
 - `true` - The payload is extracted to a separate `_payload.json` file for both the initial render and client-side navigation. The HTML is smaller and the payload file can be cached by a CDN, at the cost of one extra request on first load.
@@ -174,13 +168,13 @@ A few practical consequences to be aware of:
 - For ISR/SWR routes, CDNs can cache payload files alongside the HTML, improving client-side navigation performance for cached routes. Dynamic routes like `pages/[...slug].vue` can opt in with glob patterns such as `'/**': { isr: true }`.
 - Payloads are serialized with [devalue](https://github.com/Rich-Harris/devalue), so custom types (such as class instances) need payload plugins with custom reducers and revivers to survive the round trip.
 
-:read-more{title="Payload reducers and revivers" to="/docs/4.x/api/composables/use-nuxt-app#payload"}
+:read-more{title="Payload reducers and revivers" to="/docs/api/composables/use-nuxt-app#payload"}
 
 ## Runtime Prerender Configuration
 
 ### `prerenderRoutes`
 
-You can use this at runtime within a [Nuxt context](/docs/4.x/guide/going-further/nuxt-app#the-nuxt-context) to add more routes for Nitro to prerender.
+You can use this at runtime within a [Nuxt context](/docs/guide/going-further/nuxt-app#the-nuxt-context) to add more routes for Nitro to prerender.
 
 ```vue [app/pages/index.vue]
 <script setup>
@@ -195,7 +189,7 @@ prerenderRoutes('/api/content/article/my-article')
 </template>
 ```
 
-:read-more{title="prerenderRoutes" to="/docs/4.x/api/utils/prerender-routes"}
+:read-more{title="prerenderRoutes" to="/docs/api/utils/prerender-routes"}
 
 ### `prerender:routes` Nuxt hook
 

package/1.getting-started/16.deployment.md

@@ -38,6 +38,20 @@ It respects the following runtime environment variables:
 - `NITRO_HOST` or `HOST` (defaults to `'0.0.0.0'`)
 - `NITRO_SSL_CERT` and `NITRO_SSL_KEY` - if both are present, this will launch the server in HTTPS mode. In the vast majority of cases, this should not be used other than for testing, and the Nitro server should be run behind a reverse proxy like nginx or Cloudflare which terminates SSL.
 
+### Serving the Same Build at Multiple Paths
+
+For a normal subpath deployment, set [`app.baseURL`](/docs/api/nuxt-config#baseurl) or the `NUXT_APP_BASE_URL` environment variable.
+
+If a reverse proxy deliberately exposes the same rendered page at multiple public paths, Nuxt may replace the browser URL with the path used for server rendering during hydration. You can keep the browser URL by removing the rendered path from the payload in a server plugin:
+
+```ts [app/plugins/preserve-proxy-url.server.ts]
+export default defineNuxtPlugin((nuxtApp) => {
+  delete nuxtApp.payload.path
+})
+```
+
+Use this only when the proxy already handles assets and routing for every public path. Without the rendered path, Nuxt cannot correct a genuine mismatch between the requested URL and the server-rendered route.
+
 ### PM2
 
 [PM2](https://pm2.keymetrics.io/) (Process Manager 2) is a fast and easy solution for hosting your Nuxt application on your server or VM.
@@ -77,10 +91,10 @@ By default, the workload gets distributed to the workers with the round robin st
 
 There are two ways to deploy a Nuxt application to any static hosting services:
 
-- Static site generation (SSG) with `ssr: true` pre-renders routes of your application at build time. (This is the default behavior when running `nuxt generate`.) It will also generate `/200.html` and `/404.html` single-page app fallback pages, which can render dynamic routes or 404 errors on the client (though you may need to configure this on your static host). See [What are 200.html and 404.html?](/docs/4.x/guide/concepts/rendering#what-are-200html-and-404html).
-- Alternatively, you can prerender your site with `ssr: false` (static single-page app). This will produce HTML pages with an empty `<div id="__nuxt"></div>` where your Vue app would normally be rendered. You will lose many SEO benefits of prerendering your site, so it is suggested instead to use [`<ClientOnly>`](/docs/4.x/api/components/client-only) to wrap the portions of your site that cannot be server rendered (if any).
+- Static site generation (SSG) with `ssr: true` pre-renders routes of your application at build time. (This is the default behavior when running `nuxt generate`.) It will also generate `/200.html` and `/404.html` single-page app fallback pages, which can render dynamic routes or 404 errors on the client (though you may need to configure this on your static host). See [What are 200.html and 404.html?](/docs/guide/concepts/rendering#what-are-200html-and-404html).
+- Alternatively, you can prerender your site with `ssr: false` (static single-page app). This will produce HTML pages with an empty `<div id="__nuxt"></div>` where your Vue app would normally be rendered. You will lose many SEO benefits of prerendering your site, so it is suggested instead to use [`<ClientOnly>`](/docs/api/components/client-only) to wrap the portions of your site that cannot be server rendered (if any).
 
-Prerendered routes also emit `_payload.json` files with the data captured at build time, which Nuxt reuses during client-side navigation. Read more about [payload extraction](/docs/4.x/getting-started/prerendering#payload-extraction).
+Prerendered routes also emit `_payload.json` files with the data captured at build time, which Nuxt reuses during client-side navigation. Read more about [payload extraction](/docs/getting-started/prerendering#payload-extraction).
 
 ### Static Fallback Pages
 
@@ -99,9 +113,11 @@ export default defineNuxtConfig({
 })
 ```
 
+By default both fallbacks are empty shells. Set [`experimental.prerenderErrorPages`](/docs/guide/concepts/rendering#server-rendering-the-error-page) to server-render your `error.vue` into `404.html` at build time.
+
 Some providers use `200.html`, some use `404.html`, and some let you configure both. Check your hosting provider's static fallback or rewrite settings after deployment.
 
-:read-more{title="Nuxt prerendering" to="/docs/4.x/getting-started/prerendering"}
+:read-more{title="Nuxt prerendering" to="/docs/getting-started/prerendering"}
 
 ### Client-side Only Rendering
 
@@ -121,9 +137,9 @@ Nuxt can be deployed to several cloud providers with a minimal amount of configu
 
 ## Presets
 
-In addition to Node.js servers and static hosting services, a Nuxt project can be deployed with several well-tested presets and minimal amount of configuration.
+In addition to Node.js servers and static hosting services, a Nuxt project can be deployed with several well-tested presets and a minimal amount of configuration.
 
-You can explicitly set the desired preset in the [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) file:
+You can explicitly set the desired preset in the [`nuxt.config.ts`](/docs/directory-structure/nuxt-config) file:
 
 ```ts twoslash [nuxt.config.ts]
 // @errors: 2353