TypeStrong / ts-node

TypeScript execution and REPL for node.js
https://typestrong.org/ts-node
MIT License
12.92k stars 532 forks source link

Last release was 6 months ago... is the project dead? #2119

Open devlato opened 6 months ago

devlato commented 6 months ago

Last release was 6 months ago... is the project dead?

EvilCodeMorty commented 4 months ago

I don't know. The previous problem can't be solved by switching versions. It's over

richardsimko commented 4 months ago

We transitioned to tsx and haven't looked back

tkodev commented 4 months ago

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.

richardsimko commented 4 months ago

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)

devlato commented 4 months ago

@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.

tkodev commented 4 months ago

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

vboginskey commented 4 months ago

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:

  1. Check out the latest commit.
  2. Package it yourself with yarn pack.
  3. Put the resulting package.tgz into a package repo of your choice, or commit it to your project repo.
  4. Use the file: protocol in your package.json to consume it (if committed to repo).

This fixes the bug that otherwise prevents you from using an array extends in tsconfig.json.

erayhanoglu commented 3 months ago

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.

cjnoname commented 2 months ago

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

MuTsunTsai commented 2 months ago

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.