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
support request => Please do not submit support request here, see note at the top of this template.
Do you want to request a feature or report a bug?
A feature
What is the current behavior?
The NRM works like a charm for the current user. However, for some occasion, it's more appropriate to change the global config to make other global packages work with the new registry.
What is the expected behavior?
Please add a "-g" switch to make NRM work with global NPMRC file
What is the motivation/use case for changing the behavior?
To make the global packages work with the new registry, for example, npm-check-updates
Please tell us about your environment:
Version: 1.2.1
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
No
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
Do you want to request a feature or report a bug?
A feature
The NRM works like a charm for the current user. However, for some occasion, it's more appropriate to change the global config to make other global packages work with the new registry.
Please add a "-g" switch to make NRM work with global NPMRC file
To make the global packages work with the new registry, for example, npm-check-updates
Version: 1.2.1
No
The text was updated successfully, but these errors were encountered: