Runtime support floor
Vite 7 package.json engines node ^20.19.0 >=22.12.0
Startup fails with an engine/runtime message on a common 20.x patch level.
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 20.18 despite 'Node 20' seeming supported
Likely root cause: Startup fails with an engine/runtime message on a common 20.x patch level.
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
Startup fails with an engine/runtime message on a common 20.x patch level.
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 package.json engines node ^20.19.0 >=22.12.0
Vite 7 Node.js 20.19 22.12 engine requirement crypto.hash
Vite 7 requires Node.js version 20.19 22.12
https://raw.githubusercontent.com/vitejs/vite/main/packages/vite/package.json
https://v7.vite.dev/guide/migration.html
why Vite 7 requires Node 20.19 Node 22.12 require esm module require(esm)
"Node.js 20.19+ / 22.12+" "Vite" "require(esm)"Source Trail
GitHub source file/reference: