Hacker News Reader

Comment by azangru | Hacker News Reader

> But if you’re already familiar with TypeScript, have no fear! 5.0 is not a disruptive release, and everything you know is still applicable.

Do you know what caused the typescript team to make it a major release? Has the decorator api changed sufficiently to become a breaking change?

View on HN

Typescript always goes from version x.9 to (x+1).0. Please also note that TypeScript does not claim to strictly follow semver.

There's a section in the article called "Breaking Changes and Deprecations"

> TypeScript 5.0 has a minimum version requirement of at least Node.js 12.20 and later

https://devblogs.microsoft.com/typescript/announcing-typescr...

Internal refactors that included moving to ES modules and ended up improving overall performance and size.

It's not a major release.

There's a full page of API breaks: https://github.com/microsoft/TypeScript/wiki/API-Breaking-Ch...

Then, a new error about the deprecations of ancient options to be removed in 5.5: https://github.com/microsoft/TypeScript/issues/51909

I think "major" was used in the semver sense, which is not how the TS team chooses version numbers.

Sure, we don't bump according to semver, but it's hard to say that 5.0 _isn't_ a major release given how we used it as a way to get a bunch of breaking changes and cleanups in. It's a very opportune time as people will be forced to manually upgrade and acknowledge that something is changing.

Reply on news.ycombinator.com