8000 When process.env.NODE_PATH is set, npm-check -g still goes in… by mywildquant · Pull Request #317 · dylang/npm-check · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mywildquant
Copy link

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

@LinusU
Copy link
Collaborator
LinusU commented Nov 26, 2018

@lcxfs1991 could you review this please? ☺️

@totkeks
Copy link
totkeks commented Apr 23, 2019

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
Copy link
jacobrillema commented Aug 2, 2019

@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
Copy link
Suzakura commented Oct 13, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0