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
Currently, for me, my npm registy is https://registry.npmmirror.com, not https://registry.npmjs.org. But running attw --from-npm <pkg-name> still fetch from the default npm registry. IMO, there are 2 solutions:
allow --registry option for attw cmd.
if not pass --registry option to attw cmd, use the result of $(npm config get registry) by default
The text was updated successfully, but these errors were encountered:
Currently, for me, my npm registy is
https://registry.npmmirror.com
, nothttps://registry.npmjs.org
. But runningattw --from-npm <pkg-name>
still fetch from the default npm registry. IMO, there are 2 solutions:--registry
option forattw
cmd.--registry
option toattw
cmd, use the result of$(npm config get registry)
by defaultThe text was updated successfully, but these errors were encountered: