-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
global option doesn't allow system-wide installation of bin utils #1029
Comments
You can test the bin resolution with |
So the The problem is where those modules are actually staying on the disk. What
While what
This breaks installation as no user other than root has access to I believe the recommended solution would be to use |
@hyperknot Is that correct?
I think you meant /usr/lib/yarn_modules .. Right? |
Sorry, of course, edited my post. |
I use brew to install node on my macOS. NPM bin: I don't know if it could be useful |
My attempt to fix it |
Seems fixed |
Do you want to request a feature or report a bug?
feature
What is the current behavior?
Yarn installs to a user's or root's home folder, and links to that folder from
/usr/bin
.Since on most Linux only the current user has access to it's home folder, only the user who run the install command can use the globally installed bin utils. For anyone else they get permission denied errors when trying to run the globally installed bin util.
What is the expected behavior?
Global install of bin utils should function like they were installed system-wide, like with apt-get or npm.
Please mention your node.js, yarn and operating system version.
node: 4.6.0, yarn: 0.15.0, OS: Ubuntu 16.04.1
The text was updated successfully, but these errors were encountered: