vite-guide
Vite Guide
Establish the exact installed/target Vite, Node, and plugin versions and whether the path is client rendering, backend integration, or SSR. Check the target package's engines.node and plugin peer contracts from installed metadata or its tagged official source. Vite 7.0.0 and 8.0.0 declare ^20.19.0 || >=22.12.0: Node 21 does not satisfy this range. Do not replace that contract with "any later major" or infer it from the guide's major range.
When facts are missing, continue investigation and common guidance; defer only dependent API/configuration choices and unsupported execution. Existing failures are diagnosis and repair targets. Reconstruct migration evidence from current source if no prior report exists. Check official release support separately when maintenance status matters: this guide's diagnostic coverage of Vite 7/8 does not promise upstream maintenance or feature backports. Verify minor-specific and experimental features before using them.
Route
Start with the closest reference, then read related references directly as needed. Collect only the evidence relevant to the requested explanation, implementation, or review.
- Entry, dev server, proxy, env, assets, diagnostics: client runtime
- Imports, chunks, Rollup/Rolldown, plugins, performance: build and plugins
- Base path, caching, stale chunks, reload: deployment
- SSR middleware, module loading, separate builds, manifests, dependencies: SSR integration
- Vite 6 departure: Vite 6 to 7 migration
- Vite 7 departure and Vite 8 arrival: Vite 7 to 8 migration