-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): migrate from ts-node to tsx #25603
Merged
Merged
+546
−1,561
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
infra
Infrastructure issues (npm, GitHub Actions, releases) of this project
dependencies
Pull requests that update a dependency package or file.
scripts
Issues or pull requests regarding the scripts in scripts/.
size:l
[PR only] 101-1000 LoC changed
labels
Jan 8, 2025
caugner
force-pushed
the
migrate-from-ts-node-to-tsx
branch
from
January 8, 2025 10:30
32610ac
to
eb5a4fe
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
github-actions
bot
added
merge conflicts 🚧
This PR needs to merge latest "main" branch to resolve a merge conflict or other issue.
size:xl
[PR only] >1000 LoC changed
and removed
size:l
[PR only] 101-1000 LoC changed
labels
Jan 8, 2025
github-actions
bot
removed
the
merge conflicts 🚧
This PR needs to merge latest "main" branch to resolve a merge conflict or other issue.
label
Jan 8, 2025
queengooborg
reviewed
Jan 8, 2025
The warnings that concern us are ignored by tsx: https://github.com/privatenumber/tsx/blob/28a3e7d2b8fd72b683aab8a98dd1fcee4624e4cb/src/suppress-warnings.cts\#L12 Co-authored-by: Queen Vinyl Da.i'gyu-Kazotetsu <[email protected]>
queengooborg
approved these changes
Jan 9, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be sad to move away from SWC because it was a wonderful transpiler, but ts-node not being maintained is much more of a problem.
Elchi3
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency package or file.
infra
Infrastructure issues (npm, GitHub Actions, releases) of this project
scripts
Issues or pull requests regarding the scripts in scripts/.
size:xl
[PR only] >1000 LoC changed
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
Migrates from ts-node to tsx.
Test results and supporting details
ts-node
is no longer maintained (last update 2 years ago), and doesn't work on Node.js 22 with SWC and Import Attributes.Since
tsx
ignores the experimental warning related to "Import assertions", we no longer need the corresponding option.Related issues
Fixes #25596.