← ← Back to all products
Vite
Active
Tools & Monitoring Latest Version: 8.0.16 Latest Release: Jun 1, 2026
Vite is a next-generation frontend build tool offering a fast dev server with native ESM and an optimized Rollup/Rolldown-based production build. Each major version aligns its supported Node.js versions with Node's release schedule.
Versions
7
Latest Version
8.0.16
Active Support
3
EOL
4
Lifecycle Timeline
Today ↓
8
8
7
7
6
6
5
5
4
4
3
3
2
2
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 8 | Mar 12, 2026 | Yes | No | 8.0.16 | No | Active |
| 7 | Jun 24, 2025 | Yes | No | 7.3.5 | No | Active |
| 6 | Nov 26, 2024 | No | No | 6.4.3 | No | Active |
| 5 | Nov 16, 2023 | No | Yes | 5.4.21 | No | EOL |
| 4 | Dec 9, 2022 | No | Yes | 4.5.14 | No | EOL |
| 3 | Jul 13, 2022 | No | Yes | 3.2.11 | No | EOL |
| 2 | Feb 16, 2021 | No | Yes | 2.9.18 | No | EOL |
Frequently Asked Questions
Which versions of Vite have reached end of life?
The following Vite versions have reached end of life and no longer receive security updates: 5, 4, 3, 2. It is recommended to upgrade to a supported version.
Is it safe to continue using Vite 5?
Vite 5 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Vite?
The latest version of Vite is 8.0.16, released in the 8 release cycle.
How many versions of Vite are currently supported?
Vite currently has 3 actively supported version(s): 8, 7, 6.
When does Vite 8 reach end of life?
Vite 8 does not have a specific end-of-life date announced yet.
What should I do when Vite reaches end of life?
When a Vite version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.