yarn config set writes strings instead of booleans

[jroitgrund]

What is the current behavior?
yarn config set strict-ssl false sets strict-ssl to "false" (string) which is not respected by yarn install.

What is the expected behavior?
yarn config set strict-ssl false sets strict-ssl to false (boolean).

[jovehammer16]

I think this should be fixed by #2440

[wesm87]

This is still an issue as of v0.20.3, except now the previous workaround now longer works. Previously I could do yarn config set strict-ssl '' and it would be interpreted as a false value. Here's the current behavior:

$ yarn config set strict-ssl true --global
success Set "strict-ssl" to true.

$ yarn config set strict-ssl false --global
success Set "strict-ssl" to "false".

$ yarn config set strict-ssl '' --global
success Set "strict-ssl" to true.

This has effectively broken yarn for me until this issue is fixed, as every time yarn tries to fetch any new data I get an unable to get local issuer certificate error.

EDIT: So the error I just mentioned seems to have fixed itself. I think the issue is more the fact that the way the true / false values are printed is confusing. Sometimes the output is success Set "strict-ssl" to true. or success Set "strict-ssl" to false. and sometimes the boolean value is in quotes (success Set "strict-ssl" to "true". and success Set "strict-ssl" to "false".)

[felixfbecker]

It works for me if I use yarn config set strict-ssl false, but doesn't if I pass --strict-ssl false. Is the command line flag not supported?