[teaearlgraycold]

I personally haven’t seen this. What kind of issues have you seen?

[Tade0]

The GP could be referring to situations where libraries have strict bounds which versions of TypeScript they work with.

It's most visible in the Angular ecosystem, where both the core library and additional stuff have such bounds.

For this reason Angular updates are often a terrible experience for everyone involved.

[teaearlgraycold]

The only time I used Angular was when I had to because I was working at Google. I'd never use it outside of Google after that experience.

[PaulHoule]

I've had trouble where the build fails with various TS#### error messages, most of the time there was some change in Typescript syntax. I guess if you use those bounds you have less of those problems.

[nraf]

I’ve found Angular updates to be mostly painless since they’ve automated most of the migrations using `ng update`.

That said, I do wait 2-3 months to give time for dependencies to update.

[beanjuiceII]

I have not either, and i work with over 5 million lines of typescript codebases.