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

Fetching from Private NPM Repo Doesn't Work/Misleading User Feedback #20195

Open
jcpsimmons opened this issue Aug 17, 2023 · 0 comments
Open

Comments

@jcpsimmons
Copy link

When I try to pull down a repo from my org's private NPM repository with the following command:

NPM_CONFIG_REGISTRY="https://ghe.myorg.com/_registry/npm/@myorg/package" DENO_AUTH_TOKENS="ghp_tokentokentoken@ghe.myorg.com/_registry/npm/@myorg/package"  deno cache --node-modules-dir cache_test

I get this output

Download https://ghe.myorg.com/_registry/npm/@myorg/package/vary (59/116)

I have tried a few different permutations of the domain for DENO_AUTH_TOKENS. I can verify that using my token in a header with cURL does in fact return npm package info.

At worst private package imports are broken. At best this user feedback via the CLI isn't helpful - Download is green, there's no troubleshooting information, and it looks as if the process is just hung.

Repro with this command:
NPM_CONFIG_REGISTRY="https://google.com" deno cache --node-modules-dir googs

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

1 participant