chore!: drop Node.js < 16 support #2002
Merged
Conversation
This file contains 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
I was thining about that recently, and not sure yet myself. Node.js v16 is out of support, but their are still lots of projects/companies using it, including some of my clients (freelance), so I'm leaning towards keeping it, at least until we'd actually benefit doing something that requires v18. Note: Our test code already requires Node.js v18 I believe, but atm the released build shouldn't. |
|
We can always cut a new major version if needed. Right now we don't seem to use any features from newer Node.js so I think we can keep Node.js 16 support. |
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.
@SethFalco not sure if you want to drop support for Node.js 16 too, it doesn't seem needed AFAICT.
BTW Node.js 14 wasn't tested on CI on main.