bump minimum node version to 20.19#10876
Merged
NullVoxPopuli merged 1 commit intomasterfrom Dec 6, 2025
Merged
Conversation
NullVoxPopuli
approved these changes
Dec 5, 2025
void-mAlex
approved these changes
Dec 6, 2025
Member
|
This should be fine, since our minimum Node was already 20. The new version of broccoli also requires this minimum node version. |
Merged
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
4 participants
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.
The thing that seems to be blocking me on #10873 is that warp-drive now requires you to be on a version of node that supports require(esm). This means that we have a new minimum minor version of node that we can support with the current dependencies as defined in the blueprints.
I don't know if we need to update anything in our node support documentation for this 🤔