Is there any chance that the yarn uses a configuration from npm? All necessary settings exist in the file .npmrc, and the yarn should also use them.
One of the standard corporate proxy errors is that the thread cannot verify the first certificate.
The following sentence - given as an answer in similar questions -:
yarn config set "strict-ssl" false -g
does not work because SSL is not the only reason. Proxy settings (etc.) should also be migrated.
I accidentally found an npm package called yarnrc that gives us the ability to change various yarn settings, but I could not find any solution, so that the yarn inherits the same configuration from npmrc.
Current work around the proxy setting. Please consider the string variable here in the comment.
source
share