From dae3259fd17866c189c5e8b3a7968f515b1af4ca Mon Sep 17 00:00:00 2001 From: isaacs Date: Fri, 18 Feb 2011 20:59:57 -0800 Subject: [PATCH] You can't please everyone. Don't try to be secure if it'll fail. If someone really wants to encourage this all the time, then they can do `npm config set unsafe-perm false` explicitly. In the npm 1.0 future, it will probably require sudo for global installing no matter what, and use this behavior for local installing. Since so many people have npm installing in their home dir, requiring sudo is causing more trouble than it's worth. --- lib/utils/default-config.js | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/utils/default-config.js b/lib/utils/default-config.js index b4ae5701a4ef1..21a0b3818be98 100644 --- a/lib/utils/default-config.js +++ b/lib/utils/default-config.js @@ -50,6 +50,7 @@ module.exports = || process.platform === "cygwin" || !( process.getuid && process.setuid && process.getgid && process.setgid ) + || process.getuid() !== 0 , "update-dependents" : true , usage : false , user : "nobody"