title: Does yarn add package --build-from-source behave like npm install package --build-from-source when passing node-gyp flags to packages?
body: <p>It looks like <code>yarn</code> does not pass node-gyp flags to native packages the way <code>npm</code> does.</p>
  
  <p>For example when attempting to install sqlite3@3.1.6 with:</p>
  
  <pre><code>npm install sqlite3@3.1.6 \
    --build-from-source \
    --sqlite_libname=sqlcipher \
    --sqlite=`brew --prefix` \
    --verbose
  </code></pre>
  
  <p>we get a successful installation of sqlite3 with sqlcipher extensions, due to passing <code>--sqlite_libname</code> and <code>--sqlite</code>, which are <a href="https://github.com/mapbox/node-sqlite3/blob/d18c1e97de9478aab27067638899b068e6d8ed03/binding.gyp#L3" rel="noreferrer">specified</a> in sqlite3's <code>binding.gyp</code>.</p>
  
  <p>But, when attempting to use <code>yarn</code>, and running what I would think to be the equivalent command, it looks like the flags aren't honored:</p>
  
  <pre><code>yarn add sqlite3@3.1.6 \
    --force \
    --build-from-source \
    --sqlite_libname=sqlcipher \
    --sqlite=`brew --prefix` \
    --verbose
  </code></pre>
  
  <p>With <code>npm</code> unrecognized command line arguments are converted to gyp flags. </p>
  
  <p>With <code>yarn</code> that doesn't seem to work.</p>
  
  <p>Is there a way to get this functionality with <code>yarn</code>?</p>