Closed gustavnikolaj closed 8 years ago
I have whipped up an example, but I don't really now how to test it with the current test suite. I have tested it locally, and I can now install private scoped modules from the registries defined in the .npmrc file.
This resolves https://github.com/jspm/npm/issues/80.
Oh, sorry for missing that one. I originally posted this issue in the jspm-cli repo, as I didn't yet realize that this were the place to put it. I did my issue searching in that repository, and forgot to do it before posting this new issue :-)
Released in 0.25.1. Thanks so much @gustavnikolaj for working on this!
Thank you!
It just dawned on me that I didn't do anything special to handle authentication specific for a given scope. PR #95 means that the correct registry will be chosen for a given scope, but I didn't make any changes to use potential authentication information from .npmrc tied to that particular scope.
At work, we are using a special authentication plugin, that effectively disables the authentication when using VPN, so that's why I didn't stumple into it. I will try to see if I can come up with a way of testing this case.
@gustavnikolaj thanks I've posted https://github.com/jspm/npm/issues/98 to track this.
This issue replaces https://github.com/jspm/jspm-cli/issues/1164 as this seems to be a more fitting place for it.
A comment on that issue, also from me: