.npmrc prefix override nvm

Question

.npmrc prefix override nvm

SeeThruHead opened this issue 10 years ago · 18 comments

SeeThruHead commented 10 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

Answer 1 · 2015-01-12T23:37:47.000Z

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

Answer 2 · 2015-01-12T23:58:43.000Z

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.

Answer 3 · 2015-03-13T21:14:02.000Z

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

Answer 4 · 2015-03-13T21:23:02.000Z

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

Answer 5 · 2015-03-13T21:24:46.000Z

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

Answer 6 · 2015-03-13T21:27:59.000Z

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

Answer 7 · 2015-03-16T04:24:07.000Z

Also $PREFIX, apparently, thanks to #692.

Answer 8 · 2015-04-13T20:05:59.000Z

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.)

Answer 9 · 2015-04-13T20:11:07.000Z

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.

Answer 10 · 2015-08-27T11:54:06.000Z

Can this be closed since 7ea15a7?

Answer 11 · 2015-08-27T17:05:42.000Z

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

Answer 12 · 2015-09-23T13:20:44.000Z

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.

Answer 13 · 2017-02-27T16:28:31.000Z

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

Answer 14 · 2017-02-27T16:42:50.000Z

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

Answer 15 · 2017-02-27T17:03:11.000Z

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)

Answer 16 · 2017-02-27T17:05:20.000Z

@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 :-)

Answer 17 · 2017-02-27T17:09:32.000Z

@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!

Answer 18 · 2019-05-01T14:36:01.000Z

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