Possible to set the global install path #630

fortes · 2016-10-11T16:20:44Z

This is a feature (or perhaps documentation request).

When I run the following:

yarn global add create-react-app

Yarn will try to symlink into /usr/bin which requires sudo. With NPM, I've set my global packages to install into a user directory that is then added to my $PATH.

Is it possible to set a global directory via config somehow?

I've tried the following to no avail:

yarn add create-react-app -g --global-folder ~/bin (installs into ~/node_modules)
yarn global add create-react-app --global-folder ~/bin (still goes for /usr/bin)

This is all running on Debian 8.5

The text was updated successfully, but these errors were encountered:

sebmck · 2016-10-11T16:25:16Z

It's not currently supported but we can definently add an option.

theduke · 2016-10-11T16:30:06Z

This is a really important feature and a must have IMO.

So +1.

ef4 · 2016-10-11T16:45:23Z

If you install node to a user-owned location and set your own PATH, this already appears to work.

I always unpack node to a place like ~/Library/node-v6.7.0-darwin-x64, symlink that to ~/Library/node, and then add ~/Library/node/bin to PATH. Under those conditions, yarn correctly puts globals in the same place npm does, and sudo is not required.

kylecordes · 2016-10-11T21:24:56Z

This feature is very helpful for people who are unable to (or merely inclined against) running package installation operations, which sometimes download and execute staggering amounts of code of questionable provenance, as root.

ljharb · 2016-10-11T23:01:02Z

The npm option here is --prefix, so although it's very not recommended to use it, it'd be good to keep the same terminology.

markrian · 2016-10-12T09:52:24Z

Rather than pass an option to npm, I have prefix=${HOME}/.local in my ~/.npmrc. It'd be great if yarn respected that (and other config settings), so that it could a true drop-in replacement for npm.

victornoel · 2016-10-12T11:23:28Z

Notice that you can already add ~/.yarn-cache/.global/node_modules/.bin/ (aka what is outputed by yarn global bin) to your PATH, the only problem is the linking to /usr/bin that should be easy to disable!

vitorgalvao · 2016-10-13T19:00:23Z

Notice that you can already add (…) to your PATH

Instead of adding another directory to my PATH (which then means I’d have to do so in every other tool as well) I’d rather be able to set an option to link the binaries to wherever I want at install time.

sandys · 2016-10-28T06:06:31Z

is this going to be fixed or is this a wont fix. its seems to be one of the most requested bugs.

related ones: #1389, #1388, #1321, #1226, #1194, #1151, #1060, #1029, #927 (comment), #630, #1370

dheerajbhaskar · 2016-11-01T18:00:18Z

#1600 might also be related

sebmck · 2016-11-03T14:00:06Z

Created #1654 to fix this, pending approval.

sebmck · 2016-11-03T14:02:06Z

Linked PR makes it possible to do:

$ yarn global add react-native-cli --prefix /my-custom-prefix

vitorgalvao · 2016-11-03T14:41:32Z

Linked PR makes it possible to do:
$ yarn global add react-native-cli --prefix /my-custom-prefix

What would be the correct way to make such a prefix permanent? Is there a line we can add to .bashrc (or whatever)?

…#1654)

* master: (66 commits) Add --no-bin-links flag - fixes yarnpkg#929 (yarnpkg#1651) Add option to change the prefix of the global bin folder - fixes yarnpkg#630 (yarnpkg#1654) patterns -> filteredPatterns Add helpful nudge to yarnpkg/rfcs on issue template (yarnpkg#1650) Change reporter.log to console.log in generate-lock-entry command - fixes yarnpkg#644 (yarnpkg#1652) Fixed add command flag (yarnpkg#1653) Nested executables fix (yarnpkg#1210) Added short-flags for yarn add (yarnpkg#1618) Add name lookups to ls command - fixes yarnpkg#1599 (yarnpkg#1643) Disable flaky secureUrl test (yarnpkg#1644) Add unit tests for `yarn why`. (yarnpkg#1544) Refine flow type for config.generateHardModulePath (yarnpkg#1642) Use ~/Library/Caches as default cache location on OSX - fixes yarnpkg#1637 (yarnpkg#1638) Update aliases.js (yarnpkg#1635) Update aliases.js (yarnpkg#1634) Add webhook to archive AppVeyor build artifacts (yarnpkg#1631) Attempt to fix failing Circle CI builds (yarnpkg#1629) Adding 'yarn global upgrade'(Issue yarnpkg#776) (yarnpkg#1616) Show error message in stdout. (yarnpkg#1502) Nicer permission errors when trying to write global binaries - fixes yarnpkg#1578 (yarnpkg#1592) ...

tadeugr · 2016-12-17T18:02:31Z

It should get the default npm path:

npm config get prefix

You can run this insted

yarn global add react-native-cli --prefix $(npm config get prefix)

vitorgalvao · 2016-12-17T19:56:17Z

@tadeugr If your comment was in reply to my question, it doesn’t answer it. The question was about making a custom path the default without having to continuously use --prefix.

The answer is export PREFIX='/my-custom-prefix' in your shell’s startup files. Can’t help but think PREFIX is awfully generic and we should have something else.

tadeugr · 2016-12-17T20:37:43Z

@vitorgalvao you can play around with it. For example, I put this in my .bashrc file:

export prefix=$(npm config get prefix)
export NODE_PATH=$(npm root -g)

nachoaIvarez · 2017-01-21T16:19:45Z

Any news on your question @vitorgalvao?

vitorgalvao · 2017-01-21T16:23:07Z

@nachoaIvarez #630 (comment).

nachoaIvarez · 2017-01-21T16:25:55Z

@vitorgalvao Oh, I thought that was a wish, not the answer. Thank you.

phiresky · 2017-01-25T22:51:04Z

The answer is export PREFIX='/my-custom-prefix' in your shell’s startup files.

having to define PREFIX as a global environment variable is absolutely not a solution, because that variable used by many programs to define other things, for example make.

vitorgalvao · 2017-01-25T23:01:03Z

having to define PREFIX as a global environment variable is absolutely not a solution

It absolutely is a solution. It deliberately works! Is it a good solution? No. But I mentioned that in the next sentence:

Can’t help but think PREFIX is awfully generic and we should have something else.

I don’t think this is the place to have that discussion, though. For all intents and purposes this issue is solved and closed. Having a better global variable should be its own specific issue.

TimvdLippe · 2017-02-06T22:38:05Z

It seems that yarn config set prefix /usr/local/ works for me. Now when I do yarn global add X it creates the package in /usr/local/bin/X

vitorgalvao · 2017-02-07T00:22:00Z

Thank you @TimvdLippe. Definitely the right approach.

bastilimbach · 2017-02-10T16:02:17Z

@TimvdLippe thanks, this worked. But if you have some pre-installed packages from npm in the folder, yarn global ls doesn't list them. Anybody having the same issue?

nachoaIvarez · 2017-02-10T16:05:34Z

@bastilimbach That's expected behaviour. Yarn is looking somewhere else for global packages once you changed the place where global packages get installed. Thanks @TimvdLippe, that was definitely the solution we were looking for!

bastilimbach · 2017-02-10T16:11:09Z

@nachoaIvarez I fixed it by removing all packages and adding them back with yarn global add.

Grawl · 2017-03-01T09:30:02Z

@TimvdLippe

It seems that yarn config set prefix /usr/local/ works for me. Now when I do yarn global add X it creates the package in /usr/local/bin/X

not works with 0.21.3 on macOS

delebash · 2017-03-03T06:24:57Z

@TimvdLippe
windows 7 x64

After setting the prefix it does work but the actual node_modules are still installed in AppData\Local\Yarn\config\global\node_modules. The prefix folder just contains the .cmd files. Is there anyway to change the actual install directory?

terdia · 2017-06-23T04:49:06Z

This is the only reason why I have not switch to yarn, I need to install my front end packages in a specific folder.

sebmck added the cat-feature label Oct 11, 2016

victornoel mentioned this issue Oct 21, 2016

Location of global bin doesn't match the doc #1194

Closed

pgalkin mentioned this issue Oct 25, 2016

Global binaries don't install on Fedora 24 #1371

Closed

This was referenced Oct 31, 2016

More user-friendly error when failing to install binaries globally due to lack of permission #1578

Closed

lighthouse binaries not in $PATH after installation #1579

Open

sebmck pushed a commit that referenced this issue Nov 3, 2016

Add option o change the prefix of the global bin folder - fixes #630

7038bdc

sebmck closed this as completed Nov 3, 2016

sebmck removed the cat-feature label Nov 3, 2016

sebmck pushed a commit that referenced this issue Nov 3, 2016

Add option to change the prefix of the global bin folder - fixes #630

e1cebeb

sebmck pushed a commit that referenced this issue Nov 3, 2016

Add option to change the prefix of the global bin folder - fixes #630 (…

41fe065

…#1654)

stevenjlho mentioned this issue Dec 22, 2016

Add yarn global support fubarhouse/ansible-role-yarn#2

Closed

zmorris mentioned this issue Mar 1, 2017

global binaries don't install on mac os sierra #1321

Closed

olivierlacan mentioned this issue Apr 5, 2017

Can not run globally installed packages which are installed with yarn #2224

Open

rockchalkwushock mentioned this issue Apr 18, 2017

yarn global ls does not list global packages #3142

Closed

napcs mentioned this issue Apr 19, 2017

CLI does not work when installing with Yarn napcs/node-livereload#97

Closed

rockchalkwushock mentioned this issue Jun 10, 2017

yarn global list isn't supported #3620

Closed

rockchalkwushock mentioned this issue Jul 12, 2017

Prefix added to version of packages in package.json #3787

Closed

b0o mentioned this issue May 5, 2018

yarn global installs don't get shimmed asdf-vm/asdf-nodejs#42

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Possible to set the global install path #630

Possible to set the global install path #630

fortes commented Oct 11, 2016

sebmck commented Oct 11, 2016

theduke commented Oct 11, 2016

ef4 commented Oct 11, 2016

kylecordes commented Oct 11, 2016

ljharb commented Oct 11, 2016

markrian commented Oct 12, 2016 •

edited

Loading

victornoel commented Oct 12, 2016

vitorgalvao commented Oct 13, 2016

sandys commented Oct 28, 2016

dheerajbhaskar commented Nov 1, 2016

sebmck commented Nov 3, 2016

sebmck commented Nov 3, 2016 •

edited

Loading

vitorgalvao commented Nov 3, 2016

tadeugr commented Dec 17, 2016 •

edited

Loading

vitorgalvao commented Dec 17, 2016

tadeugr commented Dec 17, 2016

nachoaIvarez commented Jan 21, 2017

vitorgalvao commented Jan 21, 2017

nachoaIvarez commented Jan 21, 2017 •

edited

Loading

phiresky commented Jan 25, 2017

vitorgalvao commented Jan 25, 2017

TimvdLippe commented Feb 6, 2017

vitorgalvao commented Feb 7, 2017

bastilimbach commented Feb 10, 2017

nachoaIvarez commented Feb 10, 2017

bastilimbach commented Feb 10, 2017

Grawl commented Mar 1, 2017

delebash commented Mar 3, 2017

terdia commented Jun 23, 2017

Possible to set the global install path #630

Possible to set the global install path #630

Comments

fortes commented Oct 11, 2016

sebmck commented Oct 11, 2016

theduke commented Oct 11, 2016

ef4 commented Oct 11, 2016

kylecordes commented Oct 11, 2016

ljharb commented Oct 11, 2016

markrian commented Oct 12, 2016 • edited Loading

victornoel commented Oct 12, 2016

vitorgalvao commented Oct 13, 2016

sandys commented Oct 28, 2016

dheerajbhaskar commented Nov 1, 2016

sebmck commented Nov 3, 2016

sebmck commented Nov 3, 2016 • edited Loading

vitorgalvao commented Nov 3, 2016

tadeugr commented Dec 17, 2016 • edited Loading

vitorgalvao commented Dec 17, 2016

tadeugr commented Dec 17, 2016

nachoaIvarez commented Jan 21, 2017

vitorgalvao commented Jan 21, 2017

nachoaIvarez commented Jan 21, 2017 • edited Loading

phiresky commented Jan 25, 2017

vitorgalvao commented Jan 25, 2017

TimvdLippe commented Feb 6, 2017

vitorgalvao commented Feb 7, 2017

bastilimbach commented Feb 10, 2017

nachoaIvarez commented Feb 10, 2017

bastilimbach commented Feb 10, 2017

Grawl commented Mar 1, 2017

delebash commented Mar 3, 2017

terdia commented Jun 23, 2017

markrian commented Oct 12, 2016 •

edited

Loading

sebmck commented Nov 3, 2016 •

edited

Loading

tadeugr commented Dec 17, 2016 •

edited

Loading

nachoaIvarez commented Jan 21, 2017 •

edited

Loading