Vite 8 Node.js Requirements: Supported Versions & Fixes
Compare Node.js requirements for Vite 5, 6, 7 and 8, distinguish engine compatibility from support, and fix EBADENGINE errors.
Vite 8 and Vite 7 require Node.js 20.19+ or 22.12+. Prefer a maintained Node.js LTS release that satisfies your exact Vite and plugin engine ranges. An accepted engine version does not guarantee ongoing security support.
Checked 2026-09-05. Confirm the exact release notes before upgrading.Vite compatibility
| Requirement | Version or model | Result |
|---|---|---|
| Vite 8 | Node ^20.19.0 or >=22.12.0 | Current Vite major; prefer maintained Node LTS |
| Vite 7 | Node ^20.19.0 or >=22.12.0 | Check Vite release policy for maintained minor |
| Vite 6 | Node ^18.0.0, ^20.0.0 or >=22.0.0 | Legacy; do not confuse engine acceptance with support |
| Vite 5 | Node ^18.0.0 or >=20.0.0 | Legacy; plan a migration |
| Node 18 / Node 20 | Older engine-compatible lines | End of life; choose maintained Node 22 or 24 |
| Node 22 below 22.12 | Fails the Vite 7 / 8 engine range | Upgrade the Node minor release |
What this page does not prove
The matrix describes Vite package engine ranges. Plugins and templates can impose stricter requirements. Legacy Vite acceptance is not a security-support promise; consult the linked release policy before retaining an older line.
Official sources
Checked 2026-09-05. Requirements can change with new releases.
Common questions
How do I diagnose npm WARN EBADENGINE?
Run node --version, npm ls vite and npm view vite@8 engines. Compare the required range with the Node executable used in the failing terminal or CI job. Do not bypass engine checks as a fix.
How do I switch Node with nvm, fnm or Volta?
Choose one manager. For nvm: nvm install 24, then nvm use 24. For fnm: fnm install 24, then fnm use 24. For Volta: volta pin node@24. Run node --version again, update the CI runtime and reinstall from the existing lockfile with npm ci.
Can I temporarily keep an older Vite major?
Keep the existing lockfile and test on a maintained Node version accepted by that Vite release. Confirm whether the Vite line still receives fixes, then migrate one major at a time using its migration guide. Do not force-install Vite 8 onto an incompatible Node runtime.