set engine.node to ^20.19 || >=22.12#9491
Closed
dynst wants to merge 3 commits into
Closed
Conversation
Contributor
|
@dynst I appreciate the motivation, but this is a major version bump we can't do mid-cycle. npm 12 is currently in pre-release and will have the higher engine floor that will encompass the esm support |
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
2 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.
v11 updated to 20.17 and 22.9 #7831 (review) but 20.19 and 22.12 enable a major feature,
require(esm)support on by default.Updating the minimum engine version makes it possible for dependencies of npm to migrate to ESM without breaking npm.
References