Apply origin changes

github-actions · Apr 27, 2026 · May 7, 2026 · May 11, 2026 · May 21, 2026 · Jun 1, 2026
commit 6e6de4ecf44ce7b7c819f96f9d2a049cfc45157f
diff --git a/guide/api-environment-frameworks.md b/guide/api-environment-frameworks.md
@@ -31,3 +31,11 @@ await builder.buildApp()
 - **Type:** `(this: MinimalPluginContextWithoutEnvironment, builder: ViteBuilder) => Promise<void>`
 - **Kind:** `async`, `sequential`
 - **Scope:** [Global](/guide/api-environment-plugins#per-environment-hooks-and-global-hooks)
+
+const server = await createServer({
+const ssrEnvironment = server.environments.ssr
+const server = await createServer({
+const ssrEnvironment = server.environments.ssr
+  await ssrEnvironment.runner.import('virtual:entrypoint')
+ssrEnvironment.hot.send('request', serialize({ req, uniqueId }))
+  ssrEnvironment.hot.on('response', (data) => {
diff --git a/guide/api-environment.md b/guide/api-environment.md
@@ -0,0 +1 @@
+In dev, Vite executes the server code in the same Node process as the Vite dev server, giving a close approximation to the production environment. However, it is also possible for servers to run in other JS runtimes, like [Cloudflare's workerd](https://github.com/cloudflare/workerd) which have different constraints. Modern apps may also run in more than two environments, e.g. a browser, a node server, and an edge server. Vite 5 didn't allow these environments to be properly represented.
diff --git a/guide/troubleshooting.md b/guide/troubleshooting.md
@@ -1,3 +1,16 @@
 See: [Chrome issue](https://bugs.chromium.org/p/chromium/issues/detail?id=110649#c8)
 The hash key used to invalidate optimized dependencies depends on the package lock contents, the patches applied to dependencies, and the options in the Vite config file that affects the bundling of node modules. This means that Vite will detect when a dependency is overridden using a feature as [npm overrides](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides), and re-bundle your dependencies on the next server start. Vite won't invalidate the dependencies when you use a feature like [npm link](https://docs.npmjs.com/cli/v9/commands/npm-link). In case you link or unlink a dependency, you'll need to force re-optimization on the next server start by using `vite --force`. We recommend using overrides instead, which are supported now by every package manager (see also [pnpm overrides](https://pnpm.io/settings#overrides) and [yarn resolutions](https://yarnpkg.com/configuration/manifest/#resolutions)).
-Node.js inspector will generate `vite-profile-0.cpuprofile` in the root folder. You can pass `--profile <name>` (or `--profile=<name>`) to write `<name>.cpuprofile` instead. Go to https://www.speedscope.app/, and upload the CPU profile using the `BROWSE` button to inspect the result.
+Node.js inspector will generate `vite-profile-0.cpuprofile` in the root folder. You can pass `--profile <name>` (or `--profile=<name>`) to write `<name>.cpuprofile` instead. Go to https://www.speedscope.app/, and upload the CPU profile using the `BROWSE` button to inspect the result.
+### Illegal operation error when watching files
+
+If the file or directory is located on a file system that does not support file system events, Vite may be unable to watch it.
+
+An example error you may encounter is:
+
+```
+Error: EISDIR: illegal operation on a directory, watch 'C:/Users/me/project/vite.config.js'
+```
+
+For example, this can happen with a VirtualBox shared folder.
+
+To solve this, you can enable [`server.watch.usePolling`](/config/server-options#server-watch). Note that [`usePolling` leads to high CPU utilization](https://github.com/paulmillr/chokidar/tree/3.6.0#performance).
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		In dev, Vite executes the server code in the same Node process as the Vite dev server, giving a close approximation to the production environment. However, it is also possible for servers to run in other JS runtimes, like [Cloudflare's workerd](https://github.com/cloudflare/workerd) which have different constraints. Modern apps may also run in more than two environments, e.g. a browser, a node server, and an edge server. Vite 5 didn't allow these environments to be properly represented.