Path to a node's node_modules is missing from require paths about nvm HOT 5 CLOSED

Sneaking an export NODE_PATH="$NVM_DIR/$VERSION/lib/node_modules" at the bottom of use seems to do the trick (on v0.4.11 at least), though I'm not sure if it's the right thing to do? (At the very least, it probably needs to preserve the user's current value of $NODE_PATH, I'd think)

from nvm.

The behavior of NPM changed drastically when the node_modules functionality went in. Global installation is generally for stuff that has commands. If you want to use a module programmatically, do not do a global installation.

See https://github.com/isaacs/npm/blob/master/doc/faq.md#readme. Start at "How do I install something everywhere?"

Also see http://nodejs.org/docs/v0.5.4/api/modules.html#loading_from_node_modules_Folders

from nvm.

Ah hm, thanks for the tips! I'll go bug some npm folk, then - I went down that rabbit hole due to npm link sticking my in-dev package into a global node_modules :-/

Closing

from nvm.

Are you using a really old version of NPM? The version should be 1.something I think. It should not be 0.x.

Edit: Doesn't look like you are... npm link should work just fine. Go to a directory and then link whatever you want into it. It will link it to the global folder and then to your current directory. That's what the FAQ means when it says "check out npm link" I think.

from nvm.

I think this may be a special case - I effectively want a self-referential link to the current project

npm link; npm link project-name did the trick! (Though, it seems a bit awkward)

from nvm.