chore: update supported Node.js versions #119
Open
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
xiehan
force-pushed
the
node-versions-update
branch
from
2d9475d to
e3fdd22
Compare
xiehan
force-pushed
the
node-versions-update
branch
from
42b8aaa to
686eea5
Compare
12 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Node.js 17, 18, 19, 21, and (though we never supported it) 23 are all EOL: https://nodejs.org/en/about/previous-releases
Node.js 24 has just entered active development, so we might as well start building for that because we know we're going to get requests for it.
I was having trouble building locally (getting errors about
gypapparently stemming from being on Python 3.12+) so I needed to updatenode-gypandprebuild. I wonder if this is related to other users reporting having difficulties with this package.