Skip to content
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

Closed
deviprsd opened this issue Jul 14, 2021 · 4 comments
Closed

Is there support for private packages from npm? #11

deviprsd opened this issue Jul 14, 2021 · 4 comments

Comments

@deviprsd
Copy link

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?

@joeldenning
Copy link
Member

@deviprsd
Copy link
Author

deviprsd commented Jul 15, 2021

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

@joeldenning
Copy link
Member

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.

@joeldenning
Copy link
Member

This was released in https://github.com/single-spa/self-hosted-shared-dependencies/releases/tag/v1.3.0. See the new registryFetchOptions option for documentation - https://github.com/single-spa/self-hosted-shared-dependencies#config-file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants