Npm global not being used? : <p>So I've previously had some npm issues and followed some stackoverflow/github issues commands to attempt to fix them. Which worked... Kinda. Everything was fine until recently when I realised that my global npm packages are not actually being read/used.</p>

<p>So whenever I did a npm -g install xxx, or an update. It updates the global folder alright, but it's just not being used. So I went to dig a little and found this.</p>

<p>Where npm is reading/using from</p>

<pre><code>usr/local/lib/node_modules
</code></pre>

<p>Where the global is installing to</p>

<pre><code>Users/Me/.npm-global/lib/node_modules
</code></pre>

<p>So whenever I did a -g check for my modules and stuff, everything is good and updated, but when I actually try to run anything, the npm command uses the one in the older folders. So basically I can't update or install anything using -g. And nothing goes into the old folder which is the one being actually used.</p>

<p>How do I resolve this? Was some linking or profile got screwed?</p>
