-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README: remove sudo from "sudo npm install"? #1370
Comments
It does depend on how the user has installed npm in the first place. |
I asked in #npm on freenode and at least one person there was using sudo for global modules. I also noticed that cordova also suggests installing with It is possible to configure an npm installation in a directory that requires sudo to install global modules in a different directory, but there doesn't seem to be many good resources showing how to do this on google. So I figure that a lot of people are using sudo to install global modules right now. When this changes, maybe then the docs should be updated to remove sudo. |
If a text input is located in the same area as a button which was just tapped, which was probably because of a view transition, the text input gets focus 300ms later. This is an issue on Android because it also fires off a mousedown event. Resolved by remembering the touchend target then checking if it’s different from the mousedown target. Closes ionic-team#1370
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
The creator of npm back in 2010 recommended against using sudo, and AFAIK that's still the policy. http://howtonode.org/introduction-to-npm
How about making the instructions simply say
npm install -g ionic
instead ofsudo npm install -g ionic
?Besides being preferable, it's also more reliable instructions, because if the user's setup requires sudo and they don't use sudo, they'll get an error right away, where as if the user's setup doesn't require sudo and they use sudo, it will go ahead and install as root, which will make their permissions in their npm directory inconsistent.
The text was updated successfully, but these errors were encountered: