The issue that I’ve most recently encountered occurs in two different OS’s Windows and Elementary. It’s not a magic bullet.I’ve routinely been directed to what feels like a magic fix to issues when installing items over NPM. Never run as root and it will be true by default.

If the user is running as root it may cause the app to force changes that could extend beyond what a running script should have. Use this sparingly probably bad to set globally for all running scripts. This was added to help installing files into ‘safe’ locations without sudo. Sudo is causing more trouble than it’s worth.

Since so many people have npm installing in their home dir, requiring Installing no matter what, and use this behavior for local installing. In the npm 1.0 future, it will probably require sudo for global Npm config set unsafe-perm false explicitly. If someone really wants to encourage this all the time, then they can do Initially this would cause the app to either Error out when false or to toggle the user and group.īut finally, we reach the reasoning for this code (and still it’s not what many may expect). This goes all the way back to February 7th, 2011! It’s possible then you may end up having the code run as ‘root’ when installing (which could then be considered ‘unsafe’) I suppose that this isn’t ‘unsafe’ but it does force the package installer to never drop into user and group switching when installing apps. By setting unsafe-perm to true will force NPM to attempt to always run within the context of the running script. This issue that I’m facing is that the permissions my current user has are unable to create the symlinks that are being asked by the program.

Npm config set user 0