Vite 6.0 Release: New Environment API, Updated Defaults, and Growing Ecosystem

On November 26, Vite 6.0 was officially released; since Vite 5 a year ago, its adoption has surged, with weekly npm downloads jumping from 7.5 million to 17 million, and Vitest gaining a growing ecosystem.

The Vite ecosystem also welcomed new frameworks such as TanStack Start, One, and Ember, and is used by prominent companies including OpenAI, Google, Apple, Microsoft, NASA, Shopify, Cloudflare, GitLab, Reddit, and Linear.

Vite introduced a new domain vite.dev and a refreshed landing page.

Vite 6 is the most significant release since Vite 2, primarily bringing the experimental Environment API . This API formalizes the concept of environments, allowing users and framework authors to define multiple environments that match production deployment scenarios; it first appeared as the "Vite Runtime API" in Vite 5.1.

Problems solved by the Environment API:

Multi‑environment support: earlier versions only had two implicit environments (client and optional SSR); the new API enables creation of many environments such as browser, Node server, and edge server.

Dev‑build gap reduction: it allows configuring applications for all environments during both development and build, narrowing differences between them.

Backward compatibility: Vite 6 remains compatible with Vite 5, ensuring a smooth migration.

Other updates in Vite 6 include:

resolve.conditions default change: users must now manually configure resolve.conditions and ssr.resolve.conditions if they had custom values.

JSON stringification change: the json.stringify option now defaults to 'auto' , stringifying only large JSON files; json.namedExports stays enabled, and disabling can be done with json.stringify: false .

HTML resource reference extension: Vite 6 adds support for the vite-ignore attribute to opt‑out of HTML processing for specific elements.

postcss‑load‑config update: TypeScript postcss config files must be loaded with tsx or jiti , and YAML config files can be loaded with yaml .

Sass modern API default: Vite 6 uses Sass’s modern API by default; the legacy API can still be used but will be removed in Vite 7.

Library mode CSS filename: in library mode the CSS output filename defaults to the name field in package.json , unless build.lib.fileName is set; a separate build.lib.cssFileName can be used to customize the CSS filename.

Vite 6 migration guide: https://vite.dev/guide/migration.html Compiled by: Frontend Power Bank