Upgrade ts-node #3001
Merged
Upgrade ts-node #3001
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
|
Thanks for the PR! However, I find it strange that a build-time dependency to |
|
@hediet exactly. ts-node has a peer dep of typescript@>=2.7, and we had an API breaking change. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
monaco-typescript builds of TypeScript 4.6 and nightlies are failing due to a TS API change that ts-node needed to account for: microsoft/TypeScript#47921 / TypeStrong/ts-node#1648. The ts-node fix was just published to v10.6. We need this in order to get new versions of TypeScript up on the playground. Thanks!