-
-
Notifications
You must be signed in to change notification settings - Fork 533
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
Last release was 6 months ago... is the project dead? #2119
Comments
I don't know. The previous problem can't be solved by switching versions. It's over |
We transitioned to tsx and haven't looked back |
Jest still uses ts-node unfortunately, so if you're using jest you're out of luck. |
We use @swc/jest to do TS -> JS transformation, while Jest still installs ts-node it's not actually used for anything in this case (And as a bonus it's much faster) |
@koheiio @richardsimko thanks. Neither |
What I'm struggling with on my end is jest uses ts-node to read tsconfigs, which means latest typescript things like an array for the "extends" property isn't supported, and subpath imports/export resolution. If you have come across this problem and solved it, it would greatly make my life less painless! I hope there news about ts-node, whether it be good or bad. In the meantime, I'll check out swc/jest |
Not a great option, but you can:
This fixes the bug that otherwise prevents you from using an array |
If i am not wrong, tsx and swc do not support typescript decorators. We strongly uses decorators. |
swc supports decorators well, while tsx doesn't support |
My only problem with tsx is that it is based on esbuild which drops all comments on transpiling (and accordingly the author have no plans to change that), and that makes |
We use |
Last release was 6 months ago... is the project dead?
The text was updated successfully, but these errors were encountered: