TypeScript excitement 😉 Thanks to @searyanc.dev for landing the new --erasableSyntaxOnly tsconfig flag. Heading for TS 5.8 Beta next week 🎉 🔷 Guides users away from TS-only runtime features such as enum & namespace 🔷 Pairs nicely with Node's recent TypeScript support github.com/microsoft/Ty... - ThreadSky

About ThreadSky

robpalmer.bsky.social • 96 days ago

TypeScript excitement 😉

Thanks to @searyanc.dev for landing the new --erasableSyntaxOnly tsconfig flag. Heading for TS 5.8 Beta next week 🎉

🔷 Guides users away from TS-only runtime features such as enum & namespace

🔷 Pairs nicely with Node's recent TypeScript support

https://github.com/microsoft/TypeScript/pull/61011

Comments

chadsyntax.com•96 days ago

I wish we could just get enums in node to begin with 🥲

robpalmer.bsky.social•96 days ago

The detailed behavior is described here:

https://github.com/microsoft/TypeScript/issues/59601#issuecomment-2294010520

robpalmer.bsky.social•96 days ago

This is yet another example of JS ecosystem collaboration between TypeScript and Node folk 👍

https://bsky.app/profile/robpalmer.bsky.social/post/3lbl4cv2nhk2m

phoenixmatrix.bsky.social•96 days ago

I never thought I'd see the day. My dream feature.

jarredsumner.com•96 days ago

btw we’re going to go in the opposite direction of this soon. Type-only exports without the type qualifier will work at runtime without bundling

jakebailey.dev•96 days ago

A gotcha is that both Node and ts-blank-space don't handle type-only namespaces, so hopefully they all fix that soon...

jakebailey.dev•96 days ago

Now, this may not actually be final; there's just a footgun here where you can write:

export function foo() {}

declare namespace foo {
const prop = 1234;
}

And get no feedback that you accidentally told TS that "this exists, trust me" and could crash later.

But maybe it's not worth it?

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply