Post

Jake Bailey
@jakebailey.dev

Really excited that this is out the door! Super proud of the work the team has done in the past year to get this complete. Excited for the future; API stuff is in full swing, more perf improvements, and more. Please give it a try!!!

TypeScript@typescriptlang.org

📣 The moment is here. 📣 TypeScript 7 is officially released! 7️⃣ devblogs.microsoft.com/typescript/a...

devblogs.microsoft.comAnnouncing TypeScript 7.0 - TypeScriptToday we are proud to announce the availability of TypeScript 7, a 10x faster native port of TypeScript! Since its early days, TypeScript has promised to
Jake Bailey
@jakebailey.dev

Hopefully soon, but, it's a little unclear what people want when they say "Wasm", because it could mean - LSP monaco - the API in the browser - the CLI in Wasm for platforms we couldn't build which muddies the water a bit

Jake Bailey
@jakebailey.dev

but I think all three could be satisfied with one wasip1 blob or something or, tinygo, which I have been spending a bunch of time fixing to make TS work with it

0 reposts2 likes

Justin Fagnani
@justinfagnani.com

Please don't do WASI P1 though. A WASI component would be great, partially because we could build the same component interface but with additional checking and diagnostics that drops into any host accepting the compiler component's WIT interface.

Jake Bailey
@jakebailey.dev

Didn't WASI 0.3 just get released? In any case, "BigGo" doesn't have anything other than wasip1, or a JS specific integration otherwise it does mean tinygo. Interested in what shape you are expecting, of course

Justin Fagnani
@justinfagnani.com

I don't know much about tinygo, but from the little I've looked into it it seems like a good option if it works. If they prioritize Wasm, maybe they'll even support Wasm GC and WASI 0.3+ sooner than BigGo. WASI 0.3+ is supposed to get GC support in the ABI. Wasm GC might make the builds smaller.