Vite 8.3.6
Vite 8.3.6 shipped on November 5, 2026. Patch release. A long list of fixes, no new APIs. Here is what matters.
Security and Safety
- HTML attribute escaping in the dev server (#23995). Attributes rendered into generated HTML are now escaped.
- WASM outside server.fs is rejected (#23914). Files outside the allowed filesystem roots can no longer be pulled in as
.wasmimports. - ANSI escapes are sanitised for
server.forwardConsole(#23933), so a crafted page cannot paint your terminal.
Build Correctness
- Chunk import map hash signatures use stable module ids (#23976, fixes #23975). Rebuilds stop producing churned hashes for unchanged chunks.
- Dynamic imports with query strings are resolved when collecting CSS dependencies (#23909), so styles attached to those imports are no longer dropped from the bundle.
build.sourcemapis respected when it comes from the environment (#23879).build.ssr: trueuses the top-levelinputfor the SSR build (#23898).- For
ssr.target=webworker, externalrequirecalls against built-in modules are converted to imports (#23759).
Dev Server and Optimizer
- The bundled dev server accepts named imports from Node built-ins (#23858) and reloads when HMR cannot run an entry again (#23849).
- Subpath imports using
#resolve through Vite's resolver in the optimizer (#23959), and the optimizer detects its cache directory precisely (#23912). - Overlapping plugin container close calls are awaited (#23935), which removes a class of teardown race during restarts.
- Adjacent module tags on the first line of an HTML entry are cleaned up (#23823), and
$patterns in static alias replacements are preserved (#23703). - Files referenced through
new URL(..., import.meta.url)with a query or hash are watched (#23780). - pnpm's
.modules.yamlis ignored as a task input (#23634), so lockfile-adjacent churn stops retriggering work.
Dependency Bumps
@rollup/plugin-alias moves to 6.0.1, and rolldown-related dependencies were refreshed twice in this release. Non-major dependencies were updated in two passes. If you pin the optimizer internals, check those versions.
Upgrade
Install the patch with your package manager, for example pnpm add -D [email protected] or npm install -D [email protected]. There are no breaking changes; the only thing to verify is that dev-server console forwarding behaves as expected if you expose the server beyond localhost.