TypeScript 7 Support

[elliot-huffman]

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 :)

[kakasoo]

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

nonara/ts-patch#181

[samchon]

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

[ryoppippi]

WTF

[M-jerez]

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.

[CharlieDigital]

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!

[niieani]

Another idea is to go the same route as oxlint did with https://github.com/oxc-project/tsgolint/ - they patch the tsgo to expose the internals.

[elliots]

I'm using tsgolint's shims (thankyou for the idea @niieani!) in https://typical.elliots.dev/ . If that's the road you go down too, maybe we can get it distributed and maintained separately? Happy to collaborate on that or another method.

(btw the first version used typia but the compile speed wasn't there for the "validate every single function" thing I'm going for, the go version is very speedy...)

[samchon]

I'm currently concentrating autobe project, which generates backend application automatically ensuring 100% compilation success rate. I think that this project @autobe may be stabilized until April, and preparing the TS v7 update at that time was my plan. If all goes according to plan, I will probably be porting typia to the Go language around this April.

By the way, looking at @elliots invented amazing thinig, it seems ts-patch and its based libraries like typia still can keep their origin code just enduring its slow compile speed. I will also be switching to the go language when the time comes, but thank you for sharing the wonderful experience.

Personally, I know how much typia has been neglected in the front-end ecosystem due to the barrier of additional installation work called transformer, non-standard compilers such as SWC/ESBuild, and environments such as NextJS and Vite that use them.

So, I hope to move to the go language ecosystem along with the TypeScript v7 update and enjoy some of the benefits of universality. The shim implementation is amazing and beautiful, but I'm still hesitant because of the nightmares of the past, and I'd rather wait and see. I'm honestly hoping for official transformer support in TSGO, and SHIM as the last resort.

---

By the way, another type of open source collaboration is always welcome. Currently, typia is working hard on AI function calling, starting with agentica and autobe. In fact, since OpenAI announced function calling in 2023, even the typia.validate<T>() function has been specifically optimized to correct incorrectly typed arguments in AI function calls. I am also diligently adding test programs to develop accurate and reliable logic in the circumstance.

And now that I've successfully defined the compiler AST structure as a TS type and configured it with AI function calls to automate backend DB design and API development, I'm eager to invite more people to my methodology and make it a mainstream trend. @elliots seems to have all the necessary skills for this development, and I personally encourage you to pursue this field.

Anyway, please let me know if you need my help at any time. You can tackle the same topics I'm working on, or if necessary, use typia's test function datasets. I'm also learning from @elliots's code, and I'm looking to use it as a foundation for converting typia to Go.

[samchon]

Well... well... looking at the timeline and finding the progress rate of typescript-go, its release date even can be few weeks after.

I have to start studying at least Feburary.