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
They have a non-traditional SemVer policy, which includes releasing breaking changes as minor and patch releases.
In #60 and other upgrades I find these breaking changes, but they could happen to package users any time, because we don't depend on a fixed patch version (we use ^x.x.x). The user workaround would be to manually install an older version, but I can't expect that users would be able to figure out what the problem is (with the current error caused, at least).
They have a non-traditional SemVer policy, which includes releasing breaking changes as minor and patch releases.
In #60 and other upgrades I find these breaking changes, but they could happen to package users any time, because we don't depend on a fixed patch version (we use
^x.x.x
). The user workaround would be to manually install an older version, but I can't expect that users would be able to figure out what the problem is (with the current error caused, at least).There has been some discussion on mdn/browser-compat-data#7563 and other linked issues on their repo.
Ideas to solve:
The text was updated successfully, but these errors were encountered: