feat: v6 - Environment API

docs/.vitepress/config.ts

@@ -281,8 +281,8 @@ export default defineConfig({
  link: '/guide/api-javascript',
  },
  {
- text: 'Vite Runtime API',
- link: '/guide/api-vite-runtime',
+ text: 'Vite Environment API',
+ link: '/guide/api-vite-environment',
  },
  {
  text: 'Config Reference',

docs/blog/announcing-vite5-1.md

@@ -56,8 +56,6 @@ The new API brings many benefits:
 
 The initial idea [was proposed by Pooya Parsa](https://github.com/nuxt/vite/pull/201) and implemented by [Anthony Fu](https://github.com/antfu) as the [vite-node](https://github.com/vitest-dev/vitest/tree/main/packages/vite-node#readme) package to [power Nuxt 3 Dev SSR](https://antfu.me/posts/dev-ssr-on-nuxt) and later also used as the base for [Vitest](https://vitest.dev). So the general idea of vite-node has been battle-tested for quite some time now. This is a new iteration of the API by [Vladimir Sheremet](https://github.com/sheremet-va), who had already re-implemented vite-node in Vitest and took the learnings to make the API even more powerful and flexible when adding it to Vite Core. The PR was one year in the makings, you can see the evolution and discussions with ecosystem maintainers [here](https://github.com/vitejs/vite/issues/12165).
 
-Read more in the [Vite Runtime API guide](/guide/api-vite-runtime) and [give us feedback](https://github.com/vitejs/vite/discussions/15774).
-
 ## Features
 
 ### Improved support for `.css?url`

docs/config/build-options.md

@@ -192,10 +192,18 @@ When set to `true`, the build will also generate an SSR manifest for determining
 
 Produce SSR-oriented build. The value can be a string to directly specify the SSR entry, or `true`, which requires specifying the SSR entry via `rollupOptions.input`.
 
+## build.emitAssets
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+During non-client builds, static assets aren't emitted as it is assumed they would be emitted as part of the client build. This option allows frameworks to force emitting them in other environments build. It is responsibility of the framework to merge the assets with a post build step.
+
 ## build.ssrEmitAssets
 
 - **Type:** `boolean`
 - **Default:** `false`
+- **Deprecated:** use `build.emitAssets`
 
 During the SSR build, static assets aren't emitted as it is assumed they would be emitted as part of the client build. This option allows frameworks to force emitting them in both the client and SSR build. It is responsibility of the framework to merge the assets with a post build step.
 

docs/guide/api-javascript.md

@@ -135,6 +135,7 @@ interface ViteDevServer {
  /**
  * Programmatically resolve, load and transform a URL and get the result
  * without going through the http request pipeline.
+ * @deprecated use environment.transformRequest
  */
  transformRequest(
  url: string,