@nuxt/docs-nightly 5.0.0-29743111.bfb63416 → 5.0.0-29743139.d3a4e025

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.
@@ -70,7 +70,7 @@ export default defineNuxtConfig({
70
70
  Nuxt calls `bundle(nuxt)` once during `nuxt build` and `nuxt dev`, after the virtual application has been generated and the `build:before` hook has fired. Nuxt wraps your `bundle` so that any thrown error triggers the `build:error` hook automatically.
71
71
 
72
72
  ::note
73
- Only the three official builder specifiers (`@nuxt/vite-builder`, `@nuxt/webpack-builder`, `@nuxt/rspack-builder`) are recognised by name for builder-specific behaviour elsewhere in Nuxt. A custom builder still works through the generic contract described below.
73
+ Only the three official builder specifiers (`@nuxt/vite-builder`, `@nuxt/webpack-builder`, `@nuxt/rspack-builder`) are recognised by name for builder-specific behaviour elsewhere in Nuxt. A custom builder still works through the generic contract described below, but is treated as the legacy (non-Vite-environment) path.
74
74
  ::
75
75
 
76
76
  ## The Build Lifecycle
@@ -211,6 +211,12 @@ In development, a builder is also responsible for serving and hot-reloading the
211
211
 
212
212
  In dev, the build outputs are typically wired to live, in-memory sources rather than on-disk files. For instance, the SSR entry may be served from the bundler's in-memory output, and the client manifest may be computed from the dev module graph, rather than read from `nuxt.options.buildDir`.
213
213
 
214
+ ## Builders and the Vite Environment API
215
+
216
+ The contract above is deliberately builder-agnostic and works for both the legacy path (each builder runs its own bundle, and Nitro bundles the deployable separately through its own Rollup pass) and the newer [Vite Environment API](https://vite.dev/guide/api-environment) path, where Nitro runs as a Vite environment.
217
+
218
+ For a custom builder you only need to satisfy the generic contract. The Vite Environment API integration (`experimental.nitroViteEnvironment`) is specific to `@nuxt/vite-builder`; other builders, including custom ones, use the legacy Nitro Rollup path.
219
+
214
220
  ::read-more{to="/docs/4.x/guide/going-further/internals"}
215
221
  Learn more about the Nuxt interface and the build vs. runtime split.
216
222
  ::
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nuxt/docs-nightly",
3
- "version": "5.0.0-29743111.bfb63416",
3
+ "version": "5.0.0-29743139.d3a4e025",
4
4
  "repository": {
5
5
  "type": "git",
6
6
  "url": "git+https://github.com/nuxt/nuxt.git",