title: Work around to unsolved npm link symlink requires?
body: <p>When developing an NPM package, it's common to use:</p>
  
  <pre><code>npm link
  </code></pre>
  
  <p>It allows to modify <code>&lt;myPackage&gt;</code> under development without the need of publishing and unpublishing all the time! The developer can make any changes locally and see it immediately.</p>
  
  <p>It's installed into a project by using:</p>
  
  <pre><code>npm link &lt;myPackage&gt;
  </code></pre>
  
  <p>It's great, but there's a problem if the <code>&lt;myPackage&gt;</code> have a require(path).</p>
  
  <p>It'll use the real location of <code>&lt;myPackage&gt;</code> as __dirname, for example, instead of the expected location of the symlink, that should be local to the project, like a regular node_module.</p>
  
  <p>The solution I found so far, for my particular case works fine:</p>
  
  <pre><code>module.exports = {
    loadImage: function (filename) {
      var img
      if (typeof window !== 'undefined' &amp;&amp; ({}).toString.call(window) === '[object Window]') {
        try {
          img = require('../../src/images/' + filename)
        } catch (e) {
          // Development only
          img = require('./template/src/images/' + filename)
        }
      } else {
        img = '/assets/images/' + filename
      }
      return img
    }
  }
  </code></pre>
  
  <p>But as you can imagine, this cause Warning messages in the Browser. </p>
  
  <p>While I'm aware of the reason why of this problem, ideally, I'd like to suppress the error.</p>