@nuxt/docs-nightly 4.6.0-29812958.c1b50c2f → 4.6.0-29813110.5c8fe35d
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/4.api/6.nuxt-config.md +1 -1
- package/package.json +1 -1
package/4.api/6.nuxt-config.md
CHANGED
|
@@ -1317,7 +1317,7 @@ Specify the server builder to use for bundling the server part of your applicati
|
|
|
1317
1317
|
|
|
1318
1318
|
By default, Nuxt uses `@nuxt/nitro-server`, which provides standalone Nitro integration. This architecture allows for different Nitro integration patterns, such as using Nitro as a Vite plugin (with the Vite Environment API).
|
|
1319
1319
|
|
|
1320
|
-
`"nitro"` and `"vite"` are shorthands for `@nuxt/nitro-server` and `@nuxt/vite-server`. The latter is experimental and implemented with Vite alone: it
|
|
1320
|
+
`"nitro"` and `"vite"` are shorthands for `@nuxt/nitro-server` and `@nuxt/vite-server`. The latter is experimental and implemented with Vite alone: with `ssr: false` it produces a static SPA, and with SSR enabled it builds a server from the Nuxt SSR renderer whose entry exports a web-standard `{ fetch }` (`.output/server/index.mjs` serves the static output in front of it, and `nuxt preview` runs it). Every dependency is bundled into that output, so it deploys without `node_modules`. `nuxt generate` crawls that server at the end of the build and writes a static `.output/public`. It ships no server runtime, so server routes, route rules other than `prerender`, inlined styles and server components are unavailable, and modules that need a server will not work.
|
|
1321
1321
|
|
|
1322
1322
|
- **Type**: `string | { bundle: (nuxt: Nuxt) => Promise<void> }`
|
|
1323
1323
|
- **Default:** `"@nuxt/nitro-server"`
|