sync: Update Vite docs from upstream 20250624

github-actions[bot] · github-actions[bot] · commit 5f43cae56374 · 2025-06-24T01:32:56.000Z
diff --git a/docs/guide/api-environment-plugins.md b/docs/guide/api-environment-plugins.md
@@ -126,6 +126,29 @@ The hook can choose to:
   }
   ```
 
+## Per-environment State in Plugins
+
+Given that the same plugin instance is used for different environments, the plugin state needs to be keyed with `this.environment`. This is the same pattern the ecosystem has already been using to keep state about modules using the `ssr` boolean as key to avoid mixing client and ssr modules state. A `Map<Environment, State>` can be used to keep the state for each environment separately. Note that for backward compatibility, `buildStart` and `buildEnd` are only called for the client environment without the `perEnvironmentStartEndDuringDev: true` flag.
+
+```js
+function PerEnvironmentCountTransformedModulesPlugin() {
+  const state = new Map<Environment, { count: number }>()
+  return {
+    name: 'count-transformed-modules',
+    perEnvironmentStartEndDuringDev: true,
+    buildStart() {
+      state.set(this.environment, { count: 0 })
+    },
+    transform(id) {
+      state.get(this.environment).count++
+    },
+    buildEnd() {
+      console.log(this.environment.name, state.get(this.environment).count)
+    }
+  }
+}
+```
+
 ## Per-environment Plugins
 
 A plugin can define what are the environments it should apply to with the `applyToEnvironment` function.
diff --git a/docs/guide/api-plugin.md b/docs/guide/api-plugin.md
@@ -338,7 +338,6 @@ Vite plugins can also provide hooks that serve Vite-specific purposes. These hoo
   Dedicated hook for transforming HTML entry point files such as `index.html`. The hook receives the current HTML string and a transform context. The context exposes the [`ViteDevServer`](./api-javascript#vitedevserver) instance during dev, and exposes the Rollup output bundle during build.
 
   The hook can be async and can return one of the following:
-
   - Transformed HTML string
   - An array of tag descriptor objects (`{ tag, attrs, children }`) to inject to the existing HTML. Each tag can also specify where it should be injected to (default is prepending to `<head>`)
   - An object containing both as `{ html, tags }`
@@ -417,13 +416,11 @@ Vite plugins can also provide hooks that serve Vite-specific purposes. These hoo
     server: ViteDevServer
   }
   ```
-
   - `modules` is an array of modules that are affected by the changed file. It's an array because a single file may map to multiple served modules (e.g. Vue SFCs).
 
   - `read` is an async read function that returns the content of the file. This is provided because on some systems, the file change callback may fire too fast before the editor finishes updating the file and direct `fs.readFile` will return empty content. The read function passed in normalizes this behavior.
 
   The hook can choose to:
-
   - Filter and narrow down the affected module list so that the HMR is more accurate.
 
   - Return an empty array and perform a full reload:
diff --git a/docs/guide/backend-integration.md b/docs/guide/backend-integration.md
@@ -45,7 +45,6 @@ If you need a custom integration, you can follow the steps in this guide to conf
    ```
 
    In order to properly serve assets, you have two options:
-
    - Make sure the server is configured to proxy static assets requests to the Vite server
    - Set [`server.origin`](/config/server-options.md#server-origin) so that generated asset URLs will be resolved using the back-end server URL instead of a relative path
 
@@ -100,7 +99,6 @@ If you need a custom integration, you can follow the steps in this guide to conf
      }
    }
    ```
-
    - The manifest has a `Record<name, chunk>` structure
    - For entry or dynamic entry chunks, the key is the relative src path from project root.
    - For non entry chunks, the key is the base name of the generated file prefixed with `_`.
@@ -131,7 +129,6 @@ If you need a custom integration, you can follow the steps in this guide to conf
 
    Specifically, a backend generating HTML should include the following tags given a manifest
    file and an entry point:
-
    - A `<link rel="stylesheet">` tag for each file in the entry point chunk's `css` list
    - Recursively follow all chunks in the entry point's `imports` list and include a
      `<link rel="stylesheet">` tag for each CSS file of each imported chunk.
diff --git a/docs/guide/static-deploy.md b/docs/guide/static-deploy.md
@@ -265,7 +265,6 @@ You can deploy your Vite app as a Static Site on [Render](https://render.com/).
 3. Connect your GitHub/GitLab account or use a public repository.
 
 4. Specify a project name and branch.
-
    - **Build Command**: `npm install && npm run build`
    - **Publish Directory**: `dist`
 
diff --git a/docs/package.json b/docs/package.json
@@ -14,7 +14,7 @@
     "gsap": "^3.13.0",
     "vitepress": "^1.6.3",
     "vitepress-plugin-group-icons": "^1.6.0",
-    "vitepress-plugin-llms": "^1.5.0",
-    "vue": "^3.5.16"
+    "vitepress-plugin-llms": "^1.5.1",
+    "vue": "^3.5.17"
   }
 }

Original file line number	Diff line number	Diff line change
`@@ -14,7 +14,7 @@`
`14`	`14`	`"gsap": "^3.13.0",`
`15`	`15`	`"vitepress": "^1.6.3",`
`16`	`16`	`"vitepress-plugin-group-icons": "^1.6.0",`
`17`		`- "vitepress-plugin-llms": "^1.5.0",`
`18`		`- "vue": "^3.5.16"`
	`17`	`+ "vitepress-plugin-llms": "^1.5.1",`
	`18`	`+ "vue": "^3.5.17"`
`19`	`19`	`}`
`20`	`20`	`}`