You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typescript, surprisingly doesn't follow semver (microsoft/TypeScript#14116) but npm's ~ accuracy follows their policy of non-breaking patch (equivalent) changes.
For example, in typescript 4.4 the type of error in a catch clause is no longer any but unknown.
While this may not affect EUI directly, as typescript is a peer dependency, npm 7 complains that I'm installing 4.2 not 4.4.
My expectation would be for EUI to release a major version when you use a new typescript "minor", but I understand that this may be an unreasonable request, this is a highly debated (heated) topic in the npm community.
The text was updated successfully, but these errors were encountered:
Yeah using ~ makes sense, I think. I also think that would be a breaking change because some consumers would need to downgrade the version they're using.
Typescript, surprisingly doesn't follow semver (microsoft/TypeScript#14116) but
npm
's~
accuracy follows their policy of non-breaking patch (equivalent) changes.For example, in typescript 4.4 the
type
oferror
in a catch clause is no longerany
butunknown
.While this may not affect EUI directly, as typescript is a peer dependency, npm 7 complains that I'm installing
4.2
not4.4
.My expectation would be for EUI to release a major version when you use a new typescript "minor", but I understand that this may be an unreasonable request, this is a highly debated (heated) topic in the npm community.
The text was updated successfully, but these errors were encountered: