4 ms·
Regarding #1: this is not true always. Libraries publish types and their type definitions could use new TypeScript features that could force an update.
by jupp0r 4y ago
Regarding #1: this is not true always. Libraries publish types and their type definitions could use new TypeScript features that could force an update.
- tsthrowwwww 4y ago> newer versions never have breaking changes anyways. I've also seen changes to the type system that break existing library typings. (e.g. when they started strongly typing generators.) I suppose this only happens when you're using the more strict compilation settings, but that's a major draw of typescript in the first place.
- roberttod 4y agoThat's the exact case I was referring to in i) - and what drove me to write this post :)
- paxys 4y agoThis is rare (I have never run into it in many years of writing TS code and pulling repos from NPM), and if it does happen you can always ignore the definition and turn it back into a plain JS package.
- danielsju6 4y agoNot rare. Happens every 12 months or so in my experience as a library maintainer. It really sucks that Typescript, let alone .d.ts files produced by the compiler, don’t follow anything resembling semver.
- gdprrrr 4y agoThat shouldn't happen https://github.com/DefinitelyTyped/DefinitelyTyped#i-want-to-use-features-from-very-new-typescript-versions https://github.com/DefinitelyTyped/DefinitelyTyped#i-want-to...
- jupp0r 4y agoI didn't know about this, thanks.