fix: swap out ts-node for tsimp
#873
Merged
Conversation
This file contains hidden or 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
kanadgupta
added
bug
kanadgupta
changed the title
ts-node for tsimp
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.
🧰 Changes
ts-nodehas been a janky pain in the ass with modern Node.js + ESM1, so this PR swaps it out for the far more stabletsimp2.This shouldn't have any affect on end users — this is really just a change to our development / build process to get everything working again (though not entirely sure what changed in #872 that broke everything).
🧬 QA & Testing
Do tests pass?
Footnotes
see https://github.com/TypeStrong/ts-node/issues/1997 ↩
made by our boi isaac 😌 ↩