Results 1 comments of Andrej Hazucha

My observation is that cause of this issue is yarn considers `*` as newest version and `@types` packages have often dependencies versioned as `*`. According to [npm semver docs](https://docs.npmjs.com/misc/semver) `*`...