Today, we're thrilled to announce the release of the next Vite major: Vite 8.0 announcement blog post Docs (translations: 简体中文, 日本語, Español, Português, 한국어, Deutsch, فارسی) Migration Guide ⚠ BREAKING CHANGES remove import.meta.hot.accept r
Vite breaking changes
The 3 releases whose own notes call out a breaking change, out of 60 the archive holds. Scattered one per release page, this is a run nobody can see; gathered, it is the shape of how often Vite asks you to change your code.
- Tagged breaking
- 3of 60 releases
- Roughly
- 1 in 20releases held here
- Most recent
- 12 Mar 20266 months ago
- Across
- 0 daysback to 12 Mar 2026
How this is decided
A release appears here because the word breaking is in the notes its publisher wrote, not because anyone here read the diff. That cuts both ways. A release that changed an API without using the word is missing from this page, and a release that used the word about something minor is on it. It is the publisher’s own signal, reported rather than judged, which is the same rule the security page follows.
Newest first
All Vite releases⚠ BREAKING CHANGES legacy: bump modern browser threshold to import.meta.resolve support (#21662) Features legacy: bump modern browser threshold to import.meta.resolve support (#21662) (cc50822) the epic rolldown-vite merge (#21189) (4a7f8d4
⚠ BREAKING CHANGES update default browser target (#21193) Features create-vite: add AI agent experience (AX) support (#21116) (38d6011) create-vite: add ember (#20069) (2f9428d) create-vite: make vitePreprocess not the default in svelte (#2