1 points | by autobe 10 hours ago ago
7 comments
With current Node.js, you can run TypeScript directly without ttsc.
But it does not support plugin, and does not type checking either.
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.
I'm making `typia`, and it needs the type checking even in the convenient runtime like `ts-node`.
Ah so it’s for apps like typia. Congrats on the performance improvements in typia!!
How does it compare with oxlint?
`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.
With current Node.js, you can run TypeScript directly without ttsc.
But it does not support plugin, and does not type checking either.
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.
I'm making `typia`, and it needs the type checking even in the convenient runtime like `ts-node`.
Ah so it’s for apps like typia. Congrats on the performance improvements in typia!!
How does it compare with oxlint?
`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.