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
I was hitting this issue: #162 and saw that it should have been fixed in V6.6.0. But the fix to specify strict-ssl=false doesn't work for me on MacOS.
Do you know why it happens?
After a bit of digging the reasons seems to be (at least on MacOS):
The environment variable at runtime is named npm_config_strict_ssl not npm_config_strict-ssl as in the code.
When you specify --strict-ssl=false npm does not populate the variable as the string 'false'. It is an empty string. If you specify as true or omit it is set to 'true'.
NOTE: This appears like it could affect other places that pickup npm_config_* variables. e.g. npm_config_https-proxy
The text was updated successfully, but these errors were encountered:
Versions
package: mongo-memory-server
What is the Problem?
I was hitting this issue: #162 and saw that it should have been fixed in V6.6.0. But the fix to specify
strict-ssl=false
doesn't work for me on MacOS.Do you know why it happens?
After a bit of digging the reasons seems to be (at least on MacOS):
npm_config_strict_ssl
notnpm_config_strict-ssl
as in the code.--strict-ssl=false
npm does not populate the variable as the string 'false'. It is an empty string. If you specify as true or omit it is set to 'true'.NOTE: This appears like it could affect other places that pickup
npm_config_*
variables. e.g.npm_config_https-proxy
The text was updated successfully, but these errors were encountered: