.npmrc prefix override nvm #606

Closed

Closed

.npmrc prefix override nvm#606

Assignees

opened

Contributor

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

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

Member

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.

mentioned this in 2 issues

on Jan 28, 2015

mentioned this

on Feb 16, 2015

mentioned this

on Mar 10, 2015

Run correct npm completion script #427

Member

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

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

Member

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

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

mentioned this

on Mar 16, 2015

Apparently $PREFIX used by npm #692

Member

Also $PREFIX, apparently, thanks to #692.

self-assigned this

on Mar 16, 2015

Contributor

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

26 remaining items

Loading

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

ljharb

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Participants