Skip to content
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

Open
devlato opened this issue May 25, 2024 · 10 comments
Open

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

devlato opened this issue May 25, 2024 · 10 comments

Comments

@devlato
Copy link

devlato commented May 25, 2024

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

@EvilCodeMorty
Copy link

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

@richardsimko
Copy link

richardsimko commented Jul 8, 2024

We transitioned to tsx and haven't looked back

@tkodev
Copy link

tkodev commented Jul 10, 2024

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
Copy link

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
Copy link
Author

devlato commented Jul 14, 2024

@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
Copy link

tkodev commented Jul 14, 2024

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
Copy link

vboginskey commented Jul 19, 2024

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
Copy link

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
Copy link

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants