Runtime support floor
Vite 7 engines node >=22.12.0 20.19.0
CI using early Node 22 LTS fails although package policy says 22.x.
Agent Quick Fix
Repair against the current Vite contract, then keep the change narrow and source-backed.
Product: Vite
Current-contract area: Vite 7 refuses Node 22.11
Likely root cause: CI using early Node 22 LTS fails although package policy says 22.x.
Repair direction: Verifier accepts either a supported runtime pin or a justified compatible dependency pin, and rejects unsafe monkey patches. Check emitted assets and runtime behavior across the supported target.Symptom
CI using early Node 22 LTS fails although package policy says 22.x.
Why This Happens
The repository may declare a broad engine range while the current tool release silently or explicitly requires a newer patch/minor runtime.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Vite 7 engines node >=22.12.0 20.19.0
site:vite.dev guide Vite 7 Node.js version 20.19 22.12
Vite 7 Node.js 20.19+ 22.12+ official
https://vite.dev/guide/
https://vite.dev/blog/announcing-vite7