typia icon indicating copy to clipboard operation
typia copied to clipboard

TypeScript 7 Support

Open elliot-huffman opened this issue 11 months ago • 5 comments

Feature Request

TypeScript 7 no longer is built in TypeScript, it is built in the GO language: https://devblogs.microsoft.com/typescript/typescript-native-port/

I know we use TS-Patch right now, I am going to bet that TS-Patch won't work the same with a whole different language platform.

What needs changed to support this?

Let's get the discussion started, we have plenty of time before 7 becomes generally available :)

elliot-huffman avatar Mar 13 '25 15:03 elliot-huffman

Well, The ts-patch developer seems to have a different idea.

https://github.com/nonara/ts-patch/issues/181

kakasoo avatar Mar 14 '25 07:03 kakasoo

If not possible to support by ts-patch, I will support it by re-making typia by go language.

samchon avatar Mar 14 '25 10:03 samchon

WTF

ryoppippi avatar Mar 19 '25 10:03 ryoppippi

If not possible to support by ts-patch, I will support it by re-making typia by go language.

Hi @samchon, If you going to the path of building something in go please let me know. I'll be interested in helping collaborate. I'm the author of mion.io, at the moment I have built on top of @deepkit/compiler, but I more aligned with typia philosophy of being compile time only. Is just that there were some features not available in typia specially being able to use existing types from functions without having to redeclare the type of function args. So if you gonna do a rewrite I would like to help and make sure the feature is available in typia.

I know is too early to say if we gonna need a rewrite as a go does not support patching and anything written in go would be basically a custom compiled version of ts-go which is probably not the best approach.

M-jerez avatar Mar 19 '25 19:03 M-jerez

I only recently stumbled on Typia + Nestia and I'm convinced that this is possibly the absolute best approach and stack for backend development on Node at the moment because of approach of using pure TypeScript + hooking into the TypeScript compiler for AOT generation. The overall DX and capabilities of this approach feel unmatched by any of the other options out there.

For that reason, I am rooting for the success of this port!

CharlieDigital avatar Apr 13 '25 12:04 CharlieDigital