Require Node.js 22 for local development#385
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm ciwith npm's strict engine check.nvmrc, package lock, contributor guidance, deployment docs, and changelogRoot cause
The Vitest 4 toolchain depends on Node APIs unavailable in Node 18, while the repository only selected Node 22 in CI and
.nvmrc. Without package engine metadata, local installs could complete on Node 18 and then fail inside Rolldown before tests started.Impact
Developers on unsupported Node versions now receive an immediate
EBADENGINEerror with the required version. Node 22 and newer continue to install normally.Validation
npm cinpm test(4,998 tests; 100% statements and lines)npm run buildEBADENGINE)Closes #383