Vite 8.3.8
Vite 8.3.8 landed on November 11, 2026. A patch release: six fixes, two performance commits, and a revert of one of its own fixes.
TL;DR: Windows gets two quality-of-life repairs, Sass imports get cheaper, and a transform hook metadata fix shipped then came back out in the same version.
Breaking: No API Changes
Nothing in this release changes configuration or public APIs. Straight patch upgrade from 8.3.6 and 8.3.7.
Bug Fixes
- Transform hook metadata.
magicStringandastwere being dropped from the transform hook metadata object (#24012). The fix went in, then was reverted within the same release (#24065), so plugin authors relying on those fields should not expect a change here yet. - Inline worker assets. In bundled dev mode, assets referenced by inline workers are now emitted during load, closing a case where those files only appeared after a full build (#23103).
- Native loader compatibility checks. Type-only imports are skipped when Vite checks the native loader compatibility constraints, which removes a class of spurious warnings in projects that import types from config-adjacent modules (#24021).
- CSS entrypoints with
cssCodeSplit: false. A CSS file used as a build entrypoint is now rejected instead of producing broken output. Setbuild.cssCodeSplittotrue, or move the stylesheet out of the entry list (#23112). - Windows console flash. Running
yarn config getno longer pops a console window on Windows (#24013). - Dependency refresh. All non-major dependencies were bumped in one sweep (#24027).
Performance Push
- One Sass import instead of N. The CSS pipeline now imports the Sass compiler once per build rather than per file, which trims startup work on projects with large stylesheet trees (#24041).
- UNC path handling on Windows. The
net usecall is deferred until a network path is actually resolved, so ordinary local builds skip it entirely (#24014).
Tooling Notes
The repo's own lint setup changed rather than the shipped package: @types/node moved to v26 (#24029), both the vitest plugin and the vitest style rules were enabled in Oxlint (#24052, #24053), and the optimizer's external types regex now uses a non-capturing group (#24048).
Upgrade
Bump with npm install -D [email protected], or the equivalent for your package manager. If your build lists a CSS file as an entrypoint while build.cssCodeSplit is off, fix that before upgrading, because the build will now stop with an error instead of emitting partial CSS.