Show HN: TTSC – TypeScript-Go compiler and runner with transform plugins (opens in new tab)

(github.com)

2 pointsautobe22d ago8 comments

- *`ttsc`*: build, check, and transform. - *`ttsx`*: execute TypeScript with type checking. - 10x faster than `ts-node`. - type checking that `tsx` does not provide. - *`@ttsc/lint`*: lint rule violation as TS compile error. - *transformer support*: compiler-powered libraries, such as `typia`.

8 comments

k-taro5622d ago

With current Node.js, you can run TypeScript directly without ttsc.

autobeOP22d ago

But it does not support plugin, and does not type checking either.

k-taro5622d ago

If you want type checking, there’s tsc.

Do you ever really want to check types at runtime? If anything, you just want it to somehow work, right? Like Python.

1 more reply

esafak22d ago

How does it compare with oxlint?

autobeOP22d ago

`oxlint` is an independent program with typescript compiler, and @ttsc/lint is a plugin belongs to the typescript compiler.

So when using `oxlint`, you have to run it after TS compilation, but `@ttsc/lint` configured violations are detected when TS compilation.

j / k navigate · click thread line to collapse

8 comments

k-taro5622d ago

With current Node.js, you can run TypeScript directly without ttsc.

autobeOP22d ago

But it does not support plugin, and does not type checking either.

k-taro5622d ago

If you want type checking, there’s tsc.

Do you ever really want to check types at runtime? If anything, you just want it to somehow work, right? Like Python.

1 more reply

esafak22d ago

How does it compare with oxlint?

autobeOP22d ago

`oxlint` is an independent program with typescript compiler, and @ttsc/lint is a plugin belongs to the typescript compiler.

So when using `oxlint`, you have to run it after TS compilation, but `@ttsc/lint` configured violations are detected when TS compilation.

j / k navigate · click thread line to collapse