title: Yarn behind corporate proxy ignores npmrc settings
body: <p>Is there a possibility that Yarn does use the configuration from npm? All the necessary settings are existing in the <code>.npmrc</code> file and yarn should use them too.</p>
  
  <p>One of the standard errors behind corporate proxy: Yarn is unable to verify the first certificate. </p>
  
  <p>The following suggestion - given as answer in similar questions - :</p>
  
  <pre><code>yarn config set "strict-ssl" false -g
  </code></pre>
  
  <p>does not work, because the SSL is not the only reason. Proxy settings (etc) must also be carried over.</p>
  
  <p>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. </p>
  
  <p><a href="https://github.com/yarnpkg/yarn/issues/655" rel="noreferrer">Current work-around</a> over proxy parameter. Please consider the string variable <a href="https://github.com/yarnpkg/yarn/issues/980#issuecomment-257413314" rel="noreferrer">here</a> in the comment.  </p>