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 vers

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.