Changes between Version 1 and Version 2 of Ticket #5945, comment 4


Ignore:
Timestamp:
10/30/2017 11:45:23 AM (2 years ago)
Author:
juliandoucette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5945, comment 4

    v1 v2  
    22> Generally you do need super user permissions to install a npm (or anything) globally.  
    33 
    4 I would agree that it is common for an installation process to ask for administrator or super user privileges when installing for all users (e.g. a typical OS X or Windows installer). But it is certainly not true that one needs super user permissions to install npm (or anything) globally. Permission to write is necessary to install. Permission to execute in necessary to run.  
     4I would agree that it is common for an installation process to ask for administrator or super user privileges when installing for all users (e.g. a typical OS X or Windows installer). But it is certainly not true that one needs super user permissions to install npm (or anything[1]) globally. Permission to write is necessary to install. Permission to execute in necessary to run.  
    55 
    66> I think mentioning that using sudo might be required is useful, I think it should stay. If it bothers you, you could change it to say "...often requires administrator privileges..." or something like that. 
    77 
    88I agree that mentioning using sudo might be useful to *just make it work* without configuring anything. But configuring npm without sudo is easy. See https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo.md or https://docs.npmjs.com/getting-started/fixing-npm-permissions 
     9 
     10[1]: Acknowledging exceptions e.g. a program that runs another program that requires more privilages.