stop using ts-node

[ryoppippi]

Hi @samchon I'm working on migrating typia to esm first. As I'm working, I found some issues happens on ts-node. I investigate the reason and found that ts-node is not maintained for about two years. I think there are a few choices to execute ts script files directory:

• tsx
• bun
• --experimental-transform-types with node22

I think the last one is good because we can make use of node features

Please assign me if it is good for you

[samchon]

Currently, ts-node is used in many scripts.

By the way, below two scripts of test package are especially required ts-node for the transform reason.

It is okay if the change does not break below two scripts.

• debug: https://github.com/samchon/typia/blob/master/test/debug.ts
• issue: https://github.com/samchon/typia/blob/master/test/issue.ts

By the way, ts-node does not require special maintenance, because of its characteristics. Also, another typia dependent package @nestia/sdk is still keep using the ts-node to dynamically import the nestia.config.ts file that is used for the SDK generation which imports the backend server application that needs transform process too - https://nestia.io/docs/sdk/.

Thus, I cannot sure that ts-node must be replaced, and it is possible to replace the ts-node by above packages you've mentioned. tsx and bun are not supporting the transformation process of the standard TypeScript compiler. Only one thing you can choose is using the --experimental-transform-types with node22 way, but as you know, it is still experimental feature.

[xaegreal]

I would zucc some d's for node native typia integration, not gonna lie ❤️‍🔥

[ryoppippi]

@xaegreal that is zucc??

[ismailkarsli]

I see the issue about ESM-only is closed. Will this issue continue?

NodeJS has reached a sweet spot with native TS. Having to install ts-node just for Typia is a huge burden.

I hope there is at least an alternative method to ts-node like in Bun.