.npmrc prefix override nvm

Question

.npmrc prefix override nvm

SeeThruHead opened this issue 9 years ago · comments

Shane Keulen commented 9 years ago

symptoms, npm install -g npm installs npm to the wrong directory
overridden by .npmrc

removing "prefix=~/.node" from npmrc fixes the issue

osx ver: osx 10.10.1

zsh ver: zsh 5.0.5 (x86_64-apple-darwin14.0)

.npmrc:
prefix=~/.node

Wil (₩) Moore III · Answer 1 · Tue Jan 13 2015 07:37:47 GMT+0800 (China Standard Time)

I don't believe this is an nvm specific issue.

Jordan Harband · Answer 2 · Tue Jan 13 2015 07:58:43 GMT+0800 (China Standard Time)

I asked @SeeThruHead to file this - the problem as I see it is that nvm (correctly) doesn't respect npm's prefix option, but npm itself will.

I'm not sure how to handle this, but at the least, nvm could print out a warning.

Jordan Harband · Answer 3 · Sat Mar 14 2015 05:14:02 GMT+0800 (China Standard Time)

Noting from #427 that the env var $NPM_CONFIG_PREFIX also causes problems with nvm.

Kris Williams · Answer 4 · Sat Mar 14 2015 05:23:02 GMT+0800 (China Standard Time)

Maybe detect the nvm config setting upon installation and issue a stern warning?

Jordan Harband · Answer 5 · Sat Mar 14 2015 05:24:46 GMT+0800 (China Standard Time)

I'm considering making nvm refuse any operation whatsoever when problematic settings are set.

Kris Williams · Answer 6 · Sat Mar 14 2015 05:27:59 GMT+0800 (China Standard Time)

sure, just do a npm config get prefix and if it doesn't contain /.nvm/ then bail out.

Jordan Harband · Answer 7 · Mon Mar 16 2015 12:24:07 GMT+0800 (China Standard Time)

Also $PREFIX, apparently, thanks to #692.

ELLIOTTCABLE · Answer 8 · Tue Apr 14 2015 04:05:59 GMT+0800 (China Standard Time)

Ugh. Until this is patched, you might want to put a note in the README … I have no idea where my ~/.npmrc came from, but I've been complaining about being unable to update npm for ages. (At least now I know why.)

Jordan Harband · Answer 9 · Tue Apr 14 2015 04:11:07 GMT+0800 (China Standard Time)

Good idea - I'll get to one or the other hopefully in the next few weeks, but a README PR is welcome in the meantime.

Usman · Answer 10 · Thu Aug 27 2015 19:54:06 GMT+0800 (China Standard Time)

Can this be closed since 7ea15a7?

Jordan Harband · Answer 11 · Fri Aug 28 2015 01:05:42 GMT+0800 (China Standard Time)

I'm leaving it open until nvm itself refuses to do anything when a prefix is set.

Jordan Harband · Answer 12 · Wed Sep 23 2015 21:20:44 GMT+0800 (China Standard Time)

Now nvm use will refuse to work if $PREFIX or npm config get prefix is set, and will provide instructions about how to fix it.

Reopening, however, because I forgot about $NPM_CONFIG_PREFIX.

Leonardo Moreno · Answer 13 · Tue Feb 28 2017 00:28:31 GMT+0800 (China Standard Time)

Would be nice if this prefix thing could be omitted somehow through .nvmrc (just thinking).

Jordan Harband · Answer 14 · Tue Feb 28 2017 00:42:50 GMT+0800 (China Standard Time)

@leomoreno in what way? The whole concept of PREFIX is incompatible with nvm.

Leonardo Moreno · Answer 15 · Tue Feb 28 2017 01:03:11 GMT+0800 (China Standard Time)

If the suggested fix is to nvm use --delete-prefix vx.x.x, what if --delete-prefix is configurable?
I added that line to my .bash_profile so I end up with the node version I need to use.

May be I'm misunderstanding and should not nvm use --delete-prefix vx.x.x?

I was just thinking in something that let you delete-prefix at .nvmrc level, some kind of flag or similar. 🤷‍♂️ (that will make it easier to deal inside scripts)

Jordan Harband · Answer 16 · Tue Feb 28 2017 01:05:20 GMT+0800 (China Standard Time)

@elmorenocivitas --delete-prefix should be a command that's only needed once, and manually, after that your machine ideally never has a prefix to delete again :-)

Leonardo Moreno · Answer 17 · Tue Feb 28 2017 01:09:32 GMT+0800 (China Standard Time)

@ljharb for some reason it's necessary all the times here.
I'll double check the discussion above to see what's the issue.

Thanks for the fast answer!

Davis Whitehead · Answer 18 · Wed May 01 2019 22:36:01 GMT+0800 (China Standard Time)

I followed this comment to solve my issue.
#1245 (comment)