Bump ts-node to 10.8.2 #16897
Merged
Bump ts-node to 10.8.2 #16897
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
github-actions
bot
added
dependencies ⛓️
|
Can confirm 10.8.2 includes the patch -- thanks for following up on this! |
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.
Summary
This is a follow-up to #16669. That PR switched BCD to a custom fork of
ts-nodewhich integrated a specific patch for a bug fix in NodeJS 16.15. Now, ts-node 10.8.2 was released and it integrates this fix upstream, so BCD can switch back.Test results and supporting details
I produced this patch by:
package.jsonto replace"ts-node": "github:queengooborg/ts-node#patch-1-built",with"ts-node": "~10.8.2",npm i ts-node@~10.8.2to updatepackage-lock.json@queengooborg It might be easier for you to follow the above steps and to produce this patch by yourself in the first place than to verify correctness of
"integrity"fields. In that case, please do what is easiest to verify and e.g., close this PR and open a different one.Test: The CI passed when I ran it on NodeJS 16 here: https://github.com/bershanskiy/browser-compat-data/runs/7271084934
Related issues
#16669
#16668