You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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
The text was updated successfully, but these errors were encountered: