Post

We just released the beta for TypeScript 5.8! This release brings support for Node.js' require(ESM), smarter/safer checks for functions using advanced types, a few great optimizations for editor scenarios, and more. Give it a try! devblogs.microsoft.com/typescript/a...

devblogs.microsoft.comAnnouncing TypeScript 5.8 Beta - TypeScriptToday we are excited to announce the availability of TypeScript 5.8 Beta. To get started using the beta, you can get it through npm with the following command: npm install -D typescript@beta Let’s tak...

29/1/25, 8:13 pm35 reposts148 likes

Davide Aversa 🎃

@davideaversa.it

29 Jan 2025

I was just wondering today, "it is quite some time since the last TypeScript beta" :D

Rob Palmer

@robpalmer.bsky.social

29 Jan 2025

erasableSyntaxOnly is a huge win for Node today and future JS language compatibility 🎉 This is an excellent example of language stewardship.

Steven ⬢

@styfle.dev

29 Jan 2025

> be sure to keep an eye on our iteration plan The link at the bottom links to the wrong iteration plan. It currently links to 5.5 but it should link to 5.8 🙂

Fixed, thank you! 😄

@hicksyfern.bsky.social

29 Jan 2025

Oh wow the first thing is the source of 99% of my type assertions. We had to un-generic a thing today to avoid awful return type assertions and this would have solved it I reckon. Can’t wait.

Emilia

@bewitching.dev

30 Jan 2025

Saying editor scenarios, when it's effectively VSCode scenarios, feels a bit dishonest at best.

Michael Rutter

@handle.invalid

29 Jan 2025

That conditional type change is actually a pretty big win honestly. I've seen people try to use conditional types in return position countless times, and now it just works... some of the time! The erasable syntax flag might be small but might really reduce to tooling complexity of TS and node

Michael Rutter

@handle.invalid

29 Jan 2025

Only slightly salty that my one and only attempt at technical blogging has been invalidated by the conditional type change: P