Node19 base #176
Merged
Node19 base #176
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'm not sure if any extra work is required. @orta , please review. |
|
Yeah, this seems reasonable to me, deploys happen overnight - so if you send the PR for 2.0 today, I'll merge tomorrow |
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.
Closes #142
Node 19 base
After examination of https://node.green/ I found out that Node 19 capabilities are equal to Node 18.
Version 1
Due to this issue: #173 I'm making the version 1 first, having
"lib": ["es2022"], in order to support Typescript below version 5.After that version 2 can be released similar to what Node 18 base looks like currently (having es2023 lib).