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
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
Best practice for yotta modules is to use appropriately specific dependencies version spec, so that users of your module don't experience breakage when your dependencies get updated -- but several of (our) yotta modules are still using wildcard specifiers (example). It would make sense for yotta to warn you before publishing the module if you have such a version spec. See also this explanation on handling circular references using wildcards. cc @jaustin
The text was updated successfully, but these errors were encountered:
Best practice for yotta modules is to use appropriately specific dependencies version spec, so that users of your module don't experience breakage when your dependencies get updated -- but several of (our) yotta modules are still using wildcard specifiers (example). It would make sense for yotta to warn you before publishing the module if you have such a version spec. See also this explanation on handling circular references using wildcards. cc @jaustin
The text was updated successfully, but these errors were encountered: