| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Cover Node.js 20 in the test-node-version job alongside lts, 22, and 24.
There was a problem hiding this comment.
Expands the CI coverage in .github/workflows/test.yml by adding Node.js 20 to the existing test-node-version matrix, ensuring the action is validated across more supported Node versions.
Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
Vite+ requires Node ^22.18.0 || >=24.11.0, so Node 20 is unsupported. A happy-path matrix entry for 20 passed vacuously because the engine gate is only enforced by workload commands like vp install, not by vp env use or vp --version. Replace it with a negative test that runs vp install under Node 20 and asserts it fails with the incompatibility error, reproducing the rolldown CI failure.
…+ supports it) Run vp install in the matrix so Node 20 throws at Vite+'s engine gate (requires ^22.18.0 || >=24.11.0). Node 20 is kept red on purpose until Vite+ adds Node 20 support; drop the separate negative-test job.
Vite+'s bundled pnpm 11 requires node:sqlite (Node >= 22.5) and crashes on Node 20. Pin the test project to pnpm@10.34.3 so vp install runs the whole node-version matrix, including Node 20.
| Back | FazBrowse Home | New Git URL |
Adds Node 20 to the test-node-version matrix. The job now runs vp install, which enforces Vite+'s Node engine range (^22.18.0 || >=24.11.0), so Node 20 fails at the engine gate (same failure as rolldown CI).
This is intentional: Node 20 stays red until Vite+ adds Node 20 support, at which point the same matrix turns green with no test changes. lts, 22, and 24 install cleanly and pass.