docs(claude): refresh stale Node version notes#2512
Merged
Conversation
.nvmrc was 22.15.0 → 24.16.0 and the CI surface moved to a Node 22.x/24.x unit-test matrix some time ago; CLAUDE.md still claimed 22.15.0 + Node 18/20, which is wrong on both counts.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why
CLAUDE.mdclaimed.nvmrcwas22.15.0and CI ran Node 18/20. Reality:.nvmrcis24.16.0engines.nodeis>=24.16.022.xand24.x; every other job usesnode-version-file: '.nvmrc'This is a standalone doc fix — independent of the bundler/TS stack on top of it.