Fix checking collaborators when publishing to external registry #491
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I experienced issues when working with np and referencing an external registry. Although I added
to my package.json file and having an additional reference in the local .npmrc-file, the check prerequisities command required a long time and finally failed. As #339 states an npm update might help, but my version was already 6.13.1.
The reason for my issue was that the
npm.collaborators
-command missed an additional arg option "--registry https://fooregistry.tld": This PR adds the required option and thus fixes thenpm.collaborators
-command in order to allow collaborator checks for external registries.Although these issues are already closed, the error I experienced with the most-current np version comes closest to those: