search

TypeStrong / ts-node

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

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

Open devlato opened 1 month ago

devlato commented 1 month ago

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

EvilCodeMorty commented 1 week ago

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

richardsimko commented 1 week ago

We transitioned to tsx and haven't looked back

koheiio commented 1 week 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 1 week 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 6 days 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.

koheiio commented 6 days 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 18 hours 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.