-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Add install instructions for root user #3419
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
Conversation
Thanks for contributing, it's actually not the case that the root user has to be the one running the command. It depends on how your node is configured. Perhaps you could re-word the comment to say something to the effect of "Run this command with a user having enough privilege to install global modules" |
@zeekhuge updated the pull request - view changes |
Did as per your instructions. |
I was just looking at this to see why it is still open and if there is anything I could do to move the ball forward. So now that I have researched it, I don't think this is what we want to add. @zeekhuge I think that this link (https://docs.npmjs.com/getting-started/fixing-npm-permissions) covers the issue you ran into and the "right" solution. To @TylerBrock's point, we don't want to be recommending that anyone run npm as root (or sudo), and if npm is properly configured, then --unsafe-perm is unnecessary. So I'd think that we either a) change the comment to something like: If you have a permission problem when installing with -g see this link (and link to the link above). or b) just leave as is and close this pr? @zeekhuge what do you think? |
Can we get an update on this one @zeekhuge? We'd love for the instructions to be more clear and want to move forward. If we don't hear from you for a week we will close it out. |
Sorry, for replying back late, was busy with exams. I will update the PR. |
@zeekhuge updated the pull request - view changes |
Commit adds a reference to solve the EACCES error while installation.
@zeekhuge updated the pull request - view changes |
@zeekhuge I tried to find reviewers for this pull request and wanted to ping them to take another look. However, based on the blame information for the files in this pull request I couldn't find any reviewers. This sometimes happens when the files in the pull request are new or don't exist on master anymore. Is this pull request still relevant? If yes could you please rebase? In case you know who has context on this code feel free to mention them in a comment (one person is fine). Thanks for reading and hope you will continue contributing to the project. |
@TylerBrock If you could please review this request or close it if its no longer required. |
@zeekhuge updated the pull request - view changes |
@zeekhuge updated the pull request - view changes |
I am a not a nodejs developer, and it took a lot of time to figure this out.
Hope this commit will help others.