Semantic versioning seems slightly weird to even apply to something like TypeScript. You could have patch releases that fix actual compiler crashes, sure, but what is a minor release?

Surely any new feature that causes code to fail to type check when it previously would pass (or vice versa) would have to be considered a breaking change.

A similar thing applies to code formatting tools like Prettier, or any linter.

Semantic versions would at least be playing nice with how npm manages version ranges. If every release of TypeScript is breaking, then you should use major versions so that `npm update` doesn't break your project.

Yes, typescript would be at version 60 now. No, that's not a problem at all. Numbers are free.