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

[francisoud]

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]

[pascalpp]

Looks like a duplicate of #1237

[pascalpp]

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

[sebmck]

Created #1590 to fix this, pending approval.

[donaldpipowitch]

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.

[krtek]

Confirm. This is not fixed in yarn 0.20.0.

[francisoud]

Still exist in [email protected]

[DeGuitard]

And in [email protected] as well.

[francisoud]

@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...

[rally25rs]

Also if the location for this setting is going to be in .yarnrc then it should be documented at: https://yarnpkg.com/en/docs/yarnrc

[rfgamaral]

@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".

[thelaughingwolf]

Still not fixed in [email protected]

[rfgamaral]

Can we please get this reopened?

[poppinlp]

Seems still happened in 1.22.4. :)

[morigs]

The issue is still causes problems in our ci/cd pipeline 😞

This happens because yarn defaults have preference over all other options. It merges into config here and then used with the first priority here.

Possible solution is just removing this line but I need an advice from contributors about how this change can affect other modules

@sebmck what do you think?