-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there support for private packages from npm? #11
Comments
Yes, see the |
No, I meant to use it with token, username:password to access private packages from the public registry. We use that workflow, I believe there are others who do so as well |
Sorry I misread the issue. Reopening. We use npm-registry-fetch to load packages from the registry. It supports passing in username and password when calling the npm registry, so we should just add similar options to this repo and then pass them through to npm-registry-fetch. |
This was released in https://github.com/single-spa/self-hosted-shared-dependencies/releases/tag/v1.3.0. See the new |
Many organizations have private packages hosted on the public registry. I think npm-registry-fetch has a way to handle that. But I'm not sure if this package does so. It would be an easy addition with options, but if there is already a way what would it be?
The text was updated successfully, but these errors were encountered: