chore: replace ts-node with tsx #518
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
merceyz
approved these changes
Jul 12, 2024
auto-merge was automatically disabled
July 12, 2024 12:25
Head branch was pushed to by a user without write access
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.
Depends on #517Why the change?
ts-node is currently in a bit questionable shape. It barely works with newer versions od Node.js, long-standing bugs are not being addressed, TypeScript + ESM simply does not work.
I myself was affected by ts-node simply hanging on start during
yarn buildcommand on Windows.Why tsx?
While my personal favorite ts-node alternative is tsimp, tsx has seen much higher adoption so far, so I believe it's easier for others to accept it. It also uses esbuild under the hood, which we happen to already use, which results in a considerable drop of number of dependencies.