Is there a possibility that Yarn does use the configuration from npm? All the necessary settings are existing in the .npmrc
file and yarn should use them too.
One of the standard errors behind corporate proxy: Yarn is unable to verify the first certificate.
The following suggestion - given as answer in similar questions - :
yarn config set "strict-ssl" false -g
does not work, because the SSL is not the only reason. Proxy settings (etc) must also be carried over.
I accidentally have found a npm-package named yarnrc, which gives us the possibility to change between different yarn-settings, but I couldn't find any solution, so that Yarn inherits the same configuration from npmrc.
Current work-around over proxy parameter. Please consider the string variable here in the comment.