Conversation
sindresorhus
approved these changes
Mar 2, 2025
Collaborator
Author
|
Since v57 technically already had this compatibility, I think it can be released as a patch update However there's already a number of commits on main v57.0.0...main |
Owner
|
The next version will be v58. |
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.
Addresses #2561 (comment)
Particularly, the current config suggests that v57 is compatible with Node 19, but it's not.
It doesn't address the warnings issue, which can indeed be resolved by bumping Node (I'm not seeing the warning on v20.18.3)