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
We depend on some @polkadot/* packages which we lock to specific versions for development purposes, all is fine.
However yarn.lock and package-lock.json are ignored in published packages, so user installs may break if a dependency of our dependencies doesn't respect semver.
This problem is common in many package ecosystems, normally the offending package should be yanked.
However @polkadot/* moves fast and breaks stuff so we can't rely on that here.
To provide stable installs, current known options are (in order of preference):
Strongly suggest users useyarn + resolutions in their package.json
We depend on some
@polkadot/*
packages which we lock to specific versions for development purposes, all is fine.However
yarn.lock
andpackage-lock.json
are ignored in published packages, so user installs may break if a dependency of our dependencies doesn't respect semver.This problem is common in many package ecosystems, normally the offending package should be yanked.
However
@polkadot/*
moves fast and breaks stuff so we can't rely on that here.To provide stable installs, current known options are (in order of preference):
yarn
+ resolutions in theirpackage.json
shrinkwrap.json
fornpm
(risks attached)@polkadot
respects semver after doing some upgrade workThe text was updated successfully, but these errors were encountered: