node-gyp permissions issue with installing latest version (2.5.2) about npm-register HOT 5 CLOSED

On Mon, Sep 18, 2017 at 10:33 AM Jesse Bye ***@***.***> wrote: @dgautsch <https://github.com/dgautsch> definitely understand what you're saying, but we do this for a bunch of other packages and they don't have a problem. It seems to be specific to npm-register. I would go with non-sudo install if I could but we have our server automation all set to use sudo for global npm installs at this time and it would take some work to retool everything. Found this on another thread about npm global installs: Using sudo is fine. npm will not run arbitrary build scripts as root, if you're root -- it chown's the package dir to nobody and then runs scripts as nobody. If packages do other non-gyp things in their install scripts, then they are broken. Complain to the authors. If you really really need to run package scripts as root, then set the unsafe-perm config to true. Thus I'm complaining to the authors 😄 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#88 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANMfMD9mqGBqQXFc9_Xw6wJ4Of078cUks5sjqlzgaJpZM4PZUDS> .