doesn't support `$HOME/.node_modules` or `$HOME/.node_libraries`

Hi, thanks for this module! It seems to have trouble finding my packages, though:

$ readlink -m ~/.node_modules
/mnt/…/nodejs/modules
$ nodejs -e 'console.log(require.resolve("lodash")); require("resolve")("lodash", console.log);'
/mnt/…/nodejs/modules/lodash/lodash.js
{ Error: Cannot find module 'lodash' from '.'
    at /mnt/…/nodejs/modules/resolve/lib/async.js:50:31
    at processDirs (/mnt/…/nodejs/modules/resolve/lib/async.js:184:39)
    at ondir (/mnt/…/nodejs/modules/resolve/lib/async.js:199:13)
    at load (/mnt/…/nodejs/modules/resolve/lib/async.js:82:43)
    at onex (/mnt/…/nodejs/modules/resolve/lib/async.js:107:17)
    at /mnt/…/nodejs/modules/resolve/lib/async.js:12:69
    at FSReqWrap.oncomplete (fs.js:152:21) code: 'MODULE_NOT_FOUND' }

So require.resolve was able to find it, but resolve wasn’t. However, it works when I create a symlink /mnt/…/nodejs/node_modules to modules.

Update: Work-around: It also works when I pass option { paths: [process.env.HOME + "/.node_modules"] } Update 2: However, in that case I have to then explicitly resolve the returned path in order to get the exact same result.

[ljharb]

The current workaround for this is to pass [$HOME/.node_libraries, $HOME/.node_modules] as the paths option.

[mk-pmb]

However, what I can provide, is to say I didn’t write anything about NODE_PATHS in the example repo. Also git grep -nFe NODE_PATH came back empty, so it hasn’t crept in.