PNPM: pnpm outdated: UNABLE_TO_GET_ISSUER_CERT_LOCALLY when strict-ssl=false

[frederikdekegel]

pnpm version: 6.6.2

Code to reproduce the issue:

Perform the command "pnpm outdated" with strict-ssl set to false in .npmrc.

Expected behavior:

No error messages UNABLE_TO_GET_ISSUER_CERT_LOCALLY when performing pnpm outdated.

Actual behavior:

When in .npmrc strict-ssl is set to false, UNABLE_TO_GET_ISSUER_CERT_LOCALLY messages are displayed for every package first as WARNING later as ERROR.

Additional information:

Strange though that the command "pnpm install" works without a glitch and is, thus, not displaying UNABLE_TO_GET_ISSUER_CERT_LOCALLY messages even when versions of packages needed to be downloaded.

• node -v prints: 14.17.0
• Windows, macOS, or Linux?: Windows 10 Enterprise

[zkochan]

If pnpm install works, then probably we don't pass all the necessary options to the resolver in pnpm outdated.

[0xced]

On pnpm 6.23.6 and node 14.18.2, setting strict-ssl to false in the .npmrc config file did not solve the UNABLE_TO_GET_ISSUER_CERT_LOCALLY error. What worked instead was setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0.

[JohanHeyvaert]

On pnpm 6.23.6 and node 14.18.2, setting strict-ssl to false in the .npmrc config file did not solve the UNABLE_TO_GET_ISSUER_CERT_LOCALLY error. What worked instead was setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0.

Same for pnpm 7.14.2 and node 18.12.1. Thanks!

Maybe this can be documented somewhere? (if not already the case; can't find it anyway)