When process.env.NODE_PATH is set, npm-check -g still goes in…

[mywildquant]

bugfix: When process.env.NODE_PATH is set, npm-check -g still goes into globalModulesPath instead of NODE_PATH

[LinusU]

@lcxfs1991 could you review this please? ☺️

[totkeks]

Can anyone merge this pull request? That would be super handy, because I just had exactly this problem when working with NVM (node version manager) on windows, because it uses different, symlinked folders, so setting NODE_PATH helps alot.

[jacobrillema]

@totkeks I just hit the same issue. @dylang, @lcxfs1991, @LinusU or @mansona Can we please merge this in? It will greatly help us few Window users out here!

[Suzakura]

I have encountered the same error too.

===============================
The global path you are searching is: D:\xampp\node\node_modules\
[npm-check] debug
set key cwd to value C:\Users\Suzakura\AppData\Roaming\npm\node_modules
===============================

I sincerely hope that this will improve.

[stefanwascoding]

Ran into this issue on macOS 26 with a homebrew npm installation, my NODE_PATH is set to ${HOME}/.local/share/npm/lib/node_modules:/opt/homebrew/lib/node_modules, and npm-check (correctly) picks the first one as the "global path you are searching", but then sets the cwd key to the latter one.

Applying this pull request fixes the issue.