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
Referencing sindresorhus/latest-version#3, it would be great for this module to support private modules. This probably requires using the npm module rather than the HTTPS endpoint in latest-version. Assuming that won't happen, it may be a good option to allow consumers of update-notifier to specify which 'latest' module they'd like to use. Users in my situation could pass a reference to the latest module, which uses npm and the user's .npmrc with the auth token to access private modules.
The text was updated successfully, but these errors were encountered:
Referencing sindresorhus/latest-version#3, it would be great for this module to support private modules. This probably requires using the npm module rather than the HTTPS endpoint in latest-version. Assuming that won't happen, it may be a good option to allow consumers of update-notifier to specify which 'latest' module they'd like to use. Users in my situation could pass a reference to the
latest
module, which uses npm and the user's .npmrc with the auth token to access private modules.The text was updated successfully, but these errors were encountered: