Conversation
9 tasks
jeffydc
previously approved these changes
Apr 20, 2022
Contributor
Closed
4 tasks
Member
Author
bluwy
approved these changes
Apr 25, 2022
jeffydc
approved these changes
Apr 25, 2022
Member
|
Maybe it is out of scope of this PR, but you might forgot to change build settings?
|
Member
Author
I think we should do this in a separate PR 🤔 |
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
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.
Description
Fully remove support for node v12
Additional context
According to https://kangax.github.io/compat-table/es2016plus/#node14_6 I switched also to at least v14.6.0
If I'm correct, we also can target
ES2020from now on 🎉For upgrade to node v18 see #7812
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).