Skip to content
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

npm won't use the new path #24

Closed
slamidtfyn opened this issue Mar 17, 2016 · 2 comments
Closed

npm won't use the new path #24

slamidtfyn opened this issue Mar 17, 2016 · 2 comments

Comments

@slamidtfyn
Copy link

I found this extra command that convinced npm to use the new path for global install:

npm config set prefix '~/.npm-packages'

from https://docs.npmjs.com/getting-started/fixing-npm-permissions

Have tried this on a fresh ubuntu 12.04 install

@glenpike
Copy link
Owner

Hi, can you explain what you mean by the bug report - I'm not sure if this is a bug or not?

My script pretty much does what that page is explaining - it sets the config, but also tries to move any existing global packages to the new location for you. There was an issue with one of the npm commands outlined in #23 which prevented this working, but it may have been fixed now.

@glenpike
Copy link
Owner

Closing this as I don't think it's a bug - script is an alternative to the prefix (tries to help you move existing packages to new prefix automatically)

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

No branches or pull requests

2 participants