Closed
Conversation
Owner
|
The convention in the Node.js community is to support the oldest maintained LTS version, which is currently Node.js 16. |
Author
|
Yes dear, but end-of-life of Node v16 will happen like in 1 month, according https://github.com/nodejs/Release |
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.
The time has come for the Node v18 and a lot of packages are getting upgraded as it introduces a breaking change - fetch is now bundled and it generally conflicts with
node-fetchThis PR upgrades all the npm packages and bumps minimum engine supported