You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
When I try to pull down a repo from my org's private NPM repository with the following command:
I get this output
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
The text was updated successfully, but these errors were encountered: