Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

does not honor prefix set in /usr/etc/npmrc, always tries to look in /usr/lib/node_modules

See original GitHub issue

npm-check does not get the globalconfig set in /usr/ect/npmrc. It keeps looking in /usr/lib/node_modules

; globalconfig /usr/etc/npmrc
prefix = "/opt/node-global-apps"

I noted similar issues going back two years. Looks like using the global-modules and NODE_PATH do not consider that someone would be setting their own custom global path in an npmrc. Will even throw the NODE_PATH error if /usr/lib/node_modules does not exist (which it doesn’t in my case because I’ve purposely moved it)

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5

Top GitHub Comments

1reaction

dkeblercommented, Feb 26, 2020

Sadly this seems a dead project. Still at 5.9 so this issue has not been addressed. see npm-check-updates for a project that access the correct global store.

0reactions

digeomelcommented, May 27, 2020

I agree with @dkebler . I love the interactive UI of npm-check, but until this issue is fixed, I’m using npm-check-updates for the same reason. And I have read their code, even contributed to the discussion on what’s the best way to get the prefix, which apparently is not as obvious as it should be.