Yarn install hang but npm works with the same config
When I try to do a yarn install, it hangs. With npm all works fine.
My .npmrc file:
strict-ssl=false
registry=https://[url]/artifacts/repo/npm/
My .yarnrc file:
strict-ssl false
registry "https://[url]/artifacts/repo/npm/"
yarn --verbose output:
verbose 2.703 Performing "GET" request to "[url]/repo/npm/@company/coco.tools-nodejs-lite/-/@company/coco.tools-nodejs-lite-1.0.1.tgz".
[###---] 3/6
I have a private ssl registry and I've seen that when I do a npm install all packages are download from https url, but when I do a yarn install, the packages are download from http. If I delete strict-ssl false in Yarn doesn't work either. If I delete strict-ssl=false in npm I obtain this error:
...tgz failed, reason: unable to verify the first certificate
The registry doesn't work with http request, it only works with https, and when I try to access the registry by browser I obtain a SEC_ERROR_UNKNOWN_ISSUER, but I think that this isn't the problem. The problem is that Yarn's requests are done to http instead https but if I put strict-ssl=true and request are done to https Yarn hangs too...
Can anyone help me?
npm yarnpkg
add a comment |
When I try to do a yarn install, it hangs. With npm all works fine.
My .npmrc file:
strict-ssl=false
registry=https://[url]/artifacts/repo/npm/
My .yarnrc file:
strict-ssl false
registry "https://[url]/artifacts/repo/npm/"
yarn --verbose output:
verbose 2.703 Performing "GET" request to "[url]/repo/npm/@company/coco.tools-nodejs-lite/-/@company/coco.tools-nodejs-lite-1.0.1.tgz".
[###---] 3/6
I have a private ssl registry and I've seen that when I do a npm install all packages are download from https url, but when I do a yarn install, the packages are download from http. If I delete strict-ssl false in Yarn doesn't work either. If I delete strict-ssl=false in npm I obtain this error:
...tgz failed, reason: unable to verify the first certificate
The registry doesn't work with http request, it only works with https, and when I try to access the registry by browser I obtain a SEC_ERROR_UNKNOWN_ISSUER, but I think that this isn't the problem. The problem is that Yarn's requests are done to http instead https but if I put strict-ssl=true and request are done to https Yarn hangs too...
Can anyone help me?
npm yarnpkg
add a comment |
When I try to do a yarn install, it hangs. With npm all works fine.
My .npmrc file:
strict-ssl=false
registry=https://[url]/artifacts/repo/npm/
My .yarnrc file:
strict-ssl false
registry "https://[url]/artifacts/repo/npm/"
yarn --verbose output:
verbose 2.703 Performing "GET" request to "[url]/repo/npm/@company/coco.tools-nodejs-lite/-/@company/coco.tools-nodejs-lite-1.0.1.tgz".
[###---] 3/6
I have a private ssl registry and I've seen that when I do a npm install all packages are download from https url, but when I do a yarn install, the packages are download from http. If I delete strict-ssl false in Yarn doesn't work either. If I delete strict-ssl=false in npm I obtain this error:
...tgz failed, reason: unable to verify the first certificate
The registry doesn't work with http request, it only works with https, and when I try to access the registry by browser I obtain a SEC_ERROR_UNKNOWN_ISSUER, but I think that this isn't the problem. The problem is that Yarn's requests are done to http instead https but if I put strict-ssl=true and request are done to https Yarn hangs too...
Can anyone help me?
npm yarnpkg
When I try to do a yarn install, it hangs. With npm all works fine.
My .npmrc file:
strict-ssl=false
registry=https://[url]/artifacts/repo/npm/
My .yarnrc file:
strict-ssl false
registry "https://[url]/artifacts/repo/npm/"
yarn --verbose output:
verbose 2.703 Performing "GET" request to "[url]/repo/npm/@company/coco.tools-nodejs-lite/-/@company/coco.tools-nodejs-lite-1.0.1.tgz".
[###---] 3/6
I have a private ssl registry and I've seen that when I do a npm install all packages are download from https url, but when I do a yarn install, the packages are download from http. If I delete strict-ssl false in Yarn doesn't work either. If I delete strict-ssl=false in npm I obtain this error:
...tgz failed, reason: unable to verify the first certificate
The registry doesn't work with http request, it only works with https, and when I try to access the registry by browser I obtain a SEC_ERROR_UNKNOWN_ISSUER, but I think that this isn't the problem. The problem is that Yarn's requests are done to http instead https but if I put strict-ssl=true and request are done to https Yarn hangs too...
Can anyone help me?
npm yarnpkg
npm yarnpkg
edited Nov 15 '18 at 16:45
tk421
3,80651527
3,80651527
asked Nov 15 '18 at 10:31
pptoppto
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317409%2fyarn-install-hang-but-npm-works-with-the-same-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317409%2fyarn-install-hang-but-npm-works-with-the-same-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown