Yarn: strict-ssl=false in .npmrc file is not use by yarn

Created on 21 Oct 2016 · 13Comments · Source: yarnpkg/yarn

As decribe in #841:
adding a .yarnrc file in project directory with:

cafile null
strict-ssl false

works.

But I already have such settings in my .npmrc file in the same project directory:
strict-ssl=false

I was expecting it to be picked-up, but it's not...

>yarn --version
0.16.0
>node --version
v6.7.0
>ver
Microsoft Windows [version 6.1.7601]

Source

francisoud

Most helpful comment

@kittens Can you re-open it pls
You said it was pending approval and I see the fix has been merged but the bug still exist...

Can confirm, just bumped into this issue today... Surprised to see it as "fixed".

rfgamaral on 15 Jan 2019

👍7

All 13 comments

Looks like a duplicate of https://github.com/yarnpkg/yarn/issues/1237

pascalpp on 23 Oct 2016

Oh, sorry, this is about the location of the setting (in .npmrc vs .yarnrc)

pascalpp on 23 Oct 2016

Created #1590 to fix this, pending approval.

sebmck on 1 Nov 2016

This doesn't seem to be fixed for me. I use a .npmrc containing strict-ssl=false in my project root:

$ yarn config list
yarn config v0.17.8
info yarn config
{ 'version-tag-prefix': 'v',
  'version-git-tag': true,
  'version-git-sign': false,
  'version-git-message': 'v%s',
  'init-version': '1.0.0',
  'init-license': 'MIT',
  'save-prefix': '^',
  'ignore-scripts': false,
  'ignore-optional': false,
  registry: 'https://registry.yarnpkg.com',
  'strict-ssl': true,
  'user-agent': 'yarn/0.17.8 npm/? node/v6.9.1 darwin x64' }
info npm config
{ 'strict-ssl': false,
  progress: true}
✨  Done in 0.04s.

Adding strict-ssl false to my ~/.yarnrc works.