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
My team uses Artifactory as a mirror to to the public NPM registry. All packages are downloaded from Artificatory, never npm directly. However I've found that yarn can't authenticate against a private registry if the full path is given. i.e. in my .npmrc this works
This user appears to be having the same problem: #4451 (comment). NPM install works fine in either case. And with the shorter registry URL yarn install won't work without specifying the registry.
Command
yarn install
What is the current behavior?
C:\Users\pnewhook\dev\isg-core\settlement-workflow\settlement-dashboard-ui> yarn install
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://myrepo.jfrog.io/hooppisg/api/npm/my-private-registry/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.8.3.tgz: Request failed \"401 Unauthorized\"".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\me\\dev\\project\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
What is the expected behavior?
I'd expect the packages to be downloaded from my registry.
Steps to Reproduce
Configure a non-default registry in .npmrc with authentication, using the full path to the repo, not just the host.
yarn install
Environment
Yarn version:
1.22.4
Node version:
12.18.0
Platform:
win32 x64
The text was updated successfully, but these errors were encountered:
Bug description
My team uses Artifactory as a mirror to to the public NPM registry. All packages are downloaded from Artificatory, never npm directly. However I've found that yarn can't authenticate against a private registry if the full path is given. i.e. in my .npmrc this works
but this doesn't
This user appears to be having the same problem: #4451 (comment). NPM install works fine in either case. And with the shorter registry URL
yarn install
won't work without specifying the registry.Command
What is the current behavior?
What is the expected behavior?
I'd expect the packages to be downloaded from my registry.
Steps to Reproduce
Environment
Yarn version:
1.22.4
Node version:
12.18.0
Platform:
win32 x64
The text was updated successfully, but these errors were encountered: