I've been working on a small side project: type-annotationify. Migrate full-fledged TypeScript to type-annotated TypeScript compatible with the type annotations proposal and NodeJS's strip-types.

@strager Postman is an unnecessary complexity

Type-annotationify update! I've found a way to transform namespaces! It's not pretty, but it works quite nicely. Play with it here:

@Fausto95_ @robpalmer2 That would match the recent patterns of agendas, indeed

@robpalmer2 Temporal, Records & Tuples, Explicit resource management, RegExp escape, import defer 😍

@andrii_sherman HTMX won

@theo It's a web classic. S-tier bug!

@theo This explains why you're saving money on hair products for streaming day. 😉

@icrayix @theo He's using React Router

TIL: You can make YouTube auto-translate the subtitles for you! So no excuses 😉

@ThomasTorch @theo And you will donate the money for that? Every long-lived project will accumulate issues over time (or close them without fixing).

@robpalmer2 @vitalyiegorov @typescript @satanacchio Yep. It's pretty complex all in all.

@robpalmer2 I was very excited about the "Checked conditional return types", until I saw it is pretty limited. Hope they can improve on it further

RT @robpalmer2: TypeScript 5.8 Beta is released 🎉 🔶 "nodenext" gets require(ESM) 🔶 "nodenext" deprecates Import Assertions 🔷 Checked Condi…

@mattpocockuk It's time to start using `#` for internals

@trikcode A gift from the void

@mattpocockuk You want to get rid of the old syntax? Use

So this is where I now stand. My idea is to transform classes to use `public` instead of `protected` / `private` and use a local variable shadowing the actual namespace. Does anyone have suggestions or ideas? Feel free to comment on the issue or here.