ts-node
ts-node copied to clipboard
TypeStrong
Last release was 6 months ago... is the project dead?
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 tsx nor swc do type-checking our of the box though.
At the same time, ts-node does, which makes it a perfect choice for running stuff locally and for building CI automation and developer tools.
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
If you have come across this problem and solved it, it would greatly make my life less painless!
Not a great option, but you can:
- Check out the latest commit.
- Package it yourself with
yarn pack. - Put the resulting
package.tgzinto a package repo of your choice, or commit it to your project repo. - Use the
file:protocol in yourpackage.jsonto consume it (if committed to repo).
This fixes the bug that otherwise prevents you from using an array extends in tsconfig.json.
We transitioned to tsx and haven't looked back
If i am not wrong, tsx and swc do not support typescript decorators. We strongly uses decorators.
We transitioned to tsx and haven't looked back
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 /* istanbul ignore */ comments fail to work, leading to false coverage scores.
Jest still uses ts-node unfortunately, so if you're using jest you're out of luck.
We use ts-jest and that seems to work.
it seems that ts-node have no activity over 1 year. maybe we need to switch it to swc
i have create new repo and replace ts-node with swc see here. https://github.com/hyperse-io/ts-node
