Yarn global command not working

Question

I'm working with Yarn v0.16.1. If I understand correctly (according to the documentation), yarn global add <package> should be the equivalent of npm install -g <package>. However, when I run the example in the docs (with create-react-app), the command runs successfully but create-react-app is then not available from the command line. Here's the output:

$ yarn global add create-react-app
$ yarn global v0.16.1
[1/4]   Resolving packages...
[2/4]   Fetching packages...
[3/4]   Linking dependencies...
[4/4]   Building fresh packages...
success Installed create-react-app@0.6.0 with binaries:
  - create-react-app
✨  Done in 3.22s.
$ create-react-app --help
-bash: create-react-app: command not found

Doing a global install with npm has the expected result, and everything works. What am I missing with yarn?

'Modern' yarn versions have significantly changed how they handle concerns once handled by global packages. See https://next.yarnpkg.com/cli/dlx, the error message generated when you use `yarn global`, or this answer: https://stackoverflow.com/a/71809403/5440638 — Kay V, Apr 09 '22 at 15:58

score 310 · Accepted Answer · edited Aug 20 '17 at 16:25

310

You should add export PATH="$PATH:$(yarn global bin)" to your ~/.bash_profile or whatever you use. It would solve the issue.

Depending on how you installed it, Yarn's global folder varies for some reason. You can follow this issue here.

edited Aug 20 '17 at 16:25

Nathan Arthur

8,287
7
55
80

answered Oct 30 '16 at 20:40

14

You should also source the ".bash_profile" file after it's been edited to update the changes to your bash shell: `source ~/.bash_profile`. – tim-montague Apr 14 '17 at 12:12
4

On some systems you may need to run `yarn global bin` yourself and use the literal url in `~/.bash_profile` instead of the subshell, something like this: `export PATH="$PATH:/usr/local/bin"` – Nathan Arthur Aug 20 '17 at 16:28
1

I had to follow advice from this comment in the issue pointed to in the answer. ```I got global bins working by altering my path from what the docs say in the alternative installation section from export PATH="$PATH:$HOME/.yarn/bin" to export PATH="$PATH:$HOME/.yarn/bin:$HOME/.yarn-config/global/node_modules/.bin"``` https://github.com/yarnpkg/yarn/issues/1321#issuecomment-255532028 – cirovladimir May 03 '18 at 16:09
4

For Ubuntu users that come across this issue, add `export PATH="$PATH:$HOME/.config/yarn/global/node_modules/.bin"` to your ~/.bash_profile – Pitt Jul 25 '18 at 17:45
4

for zsh, just put on .zshrc – Shad Aug 10 '19 at 18:52
on ubuntu I've added export to `~/.profile` that works too – slavugan Aug 12 '20 at 15:49
fis shell: `set -Ua fish_user_paths (yarn global bin)` – Nearoo Dec 03 '20 at 08:21
sadly this line adds ugly `warning ../package.json: No license field` to every session – godblessstrawberry Mar 06 '23 at 05:37

AndrewD · Answer 2 · 2018-12-21T07:45:49.403

114

Update Dec 2018

Just updating the path didn't work for me. I had to also set the yarn prefix.

Ubuntu 18.04.1 LTS (bionic)
yarn 1.12.3
npm v3.5.2
node v8.10.0
zsh 5.4.2

Steps

Confirm your global bin path
```
yarn global bin
```

I got: /home/username/.yarn/bin

set yarn prefix:

make sure your yarn prefix is the parent directory of your bin directory. You can confirm by running
```
yarn config get prefix
```
when I ran this, my prefix was empty, so I set it:
```
yarn config set prefix ~/.yarn
```
add the following to ~/.bash_profile or ~/.bashrc
```
export PATH="$PATH:`yarn global bin`"
```
for zsh users, be sure to add this line to ~/.zshrc
restart your shell or start a new one

bash -l or zsh

edited Dec 21 '18 at 07:45

answered Dec 21 '18 at 05:16

AndrewD

4,924
3
30
32

Thanks, works perfectly ! Tested on _Ubuntu 18.04_ on _WSL_ – robe007 Jul 29 '19 at 22:48
@AndrewD This should be the accepted answer – CodeConnoisseur Mar 13 '21 at 15:21
Also worked on `Lubuntu 21.04` – Afshar Mohebi Nov 14 '21 at 10:20
Windows user here - just setting the prefix worked for me, thanks! – David Voráč Jun 29 '22 at 09:15
1

This works but not at the first zsh launch each time I open a terminal... I always have to restart zsh... – Louis Lecouturier Jul 22 '22 at 08:49
on Mac, was missing it in .zshrc, legend! – Jimmy Long Aug 02 '23 at 17:48

score 26 · Answer 3 · answered Aug 19 '19 at 14:48

26

In my case yarn global bin wasn't working.

Try a brew reinstall yarn if that's how you installed yarn

answered Aug 19 '19 at 14:48

Antoine

1,206
16
19

Thapedict · Answer 4 · 2021-06-11T15:06:03.337

13

Ran into this issue but on a Windows system. All I had to do was add the yarn global bin to the PATH variable.

setx path "%path%;c:\users\YOURUSERNAME\appdata\local\yarn\bin"

Remember to change YOURUSERNAME to your account username.

You can check where your global bin is by running

yarn global bin

And please don't forget to restart the CMD window that you're working on. Happy coding!

! WARNING !

When executing the command that %path%; in front of your yarn directory is very important. If you don't type it you will definitely replace all your system environment variables.

Option 2

Safer option would be would be to just go to System Properties > Advanced > Environment Variables > select PATH the click Edit > then append and not replace with ;c:\users\YOURUSERNAME\appdata\local\yarn\bin

edited Jun 11 '21 at 15:06

answered Feb 27 '20 at 15:03

Thapedict

363
2
9

2

Resolved my issue on Windows 10 after running 'yarn global add vuepress' and creating the read me, the 'vuepress dev' command was not able to be found prior. – Boz May 29 '20 at 09:52
2

WARNING: I executed this on PowerShell and lost all my environment variables – now Apr 12 '21 at 11:05
1

@now you probably didn't include '%PATH%;' before the yarn directory, or used single quotes. Been a victim of this too. Safer option would be to just go to System Properties > Advanced > Environment Variables ..and append that yarn directory – Thapedict Jun 11 '21 at 14:28

score 10 · Answer 5 · edited Nov 16 '19 at 05:06

10

To reinstall run below.

brew install -g yarn

// Note:(updating homebrew) for Mac users.

brew reinstall yarn

// (if yarn is still not found)

edited Nov 16 '19 at 05:06

Nick

138,499
22
57
95

answered Nov 16 '19 at 04:49

heyfranksmile

169
1
5

score 9 · Answer 6 · answered Feb 12 '21 at 04:44

9

For macOS, you just need one step,

export PATH=~/.yarn/bin:$PATH

answered Feb 12 '21 at 04:44

Harsh Patel

6,334
10
40
73

Can you explain this code please? Very useful as it helped me but I don't quite get it. – github292929 Feb 07 '22 at 03:32
@github292929 read this https://askubuntu.com/questions/720678/what-does-export-path-somethingpath-mean – Richardsondx Mar 02 '22 at 17:45
Didn't work for me on Mac – Carlos Ferreira May 02 '22 at 13:51

score 4 · Answer 7 · answered Aug 19 '22 at 19:52

4

export PATH="$PATH:$(yarn global bin)"

answered Aug 19 '22 at 19:52

DEV Tiago França

1,271
9
9

score 3 · Answer 8 · answered Sep 25 '20 at 13:39

Here's the process I used on Mac OSX El Capitan.

Try to install yarn (I used the Curl command) if you have it already. This will bring up if its already installed and will give you the current directory where it exists.

Like this:

curl -o- -L https://yarnpkg.com/install.sh | bash

It will display something like this:

Installing Yarn!
> /Users/{Your Username}/.yarn already exists, possibly from a past Yarn install.
> Remove it (rm -rf /Users/{Your Username}/.yarn) and run this script again.

Do not remove it. Move on to step 2.

Copy the directory listed above. Open your profile. I'm using zsh. So mine was ~/.zshrc. You can find yours and more info here.
Copy the following (replacing your directory and username details as necessary, the one you got from the installation error message).

alias yarn="/Users/{Your Username}/.yarn/bin/yarn"

Try to run yarn version to check if its working. If it is, you should see a version number displayed in your terminal.

That's it, and what worked for me.

score 3 · Answer 9 · answered Oct 29 '20 at 08:48

AndrewD gave a great answer, but for those on Windows it's a bit different, especially step 3.

Please do not use the command setx as @Thapedict said. It will remove all your previous paths you had and replace it with only the given directory. If you want to use setx, I think there might be a flag to make it append the existing path variables, but I don't know which one. Using only setx will not append to it.

I would just do System Properties > Advanced > Environment Variables > Edit Path > New > c:\users\YOURUSERNAME\appdata\local\yarn\bin

to make sure you don't remove your previous variables.

adding `%PATH%;` before the directory you want to include is the way you append it. If you omit %PATH%; it will most definitely replace instead of append. And wrapping with double apostrophe is also as important. https://www.windows-commandline.com/set-path-command-line/ — Thapedict, Jun 11 '21 at 14:06

score 2 · Answer 10 · answered Dec 22 '19 at 11:46

2

On Ubuntu, I fixed by installing the package like this:

sudo yarn global add <package> --prefix /usr/local

answered Dec 22 '19 at 11:46

Florian Ludewig

4,338
11
71
137

score 2 · Answer 11 · answered Aug 07 '23 at 15:19

To fix this issue in 2023:

corepack enable

I started running into this issue out of all of a sudden in July 2023 across multiple computers. I tried all different kinds of updates to my bash/zsh profiles - nothing worked except running corepack enable manually. More info on corepack here.

score 1 · Answer 12 · answered Oct 24 '19 at 08:17

When switching from bash to zsh, I got the same error, it worked for me:

in your .zshrc 

# NVM Stuff
export NVM_DIR="$HOME/.nvm"
. "$(brew --prefix nvm)/nvm.sh"

# YVM Stuff
export YVM_DIR="$HOME/.yvm"
. "$(brew --prefix yvm)/yvm.sh"

As I understand it, my mistake arose due to the lack of access to version managers

score 1 · Answer 13 · answered Jul 28 '21 at 19:32

1

I faced a similar issue on Windows after installing Yarn then Vue Cli. Packages were installed but not accessible. The problem was that the directory where yarn packages are installed is not in PATH.

The default installation directory for Yarn packages in my case was C:\Users\USERNAME\AppData\Local\Yarn

So make sure to add this directory to path.

answered Jul 28 '21 at 19:32

Denmau

231
2
5

you can quickly get the directory by `yarn global bin` – Justin Oct 29 '21 at 13:48

score 1 · Answer 14 · answered Feb 22 '23 at 22:33

It's no longer necessary to modify your path for yarn

Newer versions of yarn include yarn create and yarn exec

In the case of create-react-app you can run yarn create react-app see this blog post https://classic.yarnpkg.com/blog/2017/05/12/introducing-yarn/

To run a non-creating package like serve, you can still run it without modifying your path! After installing it with yarn global add serve try this: yarn exec serve

score 0 · Answer 15 · answered Nov 24 '21 at 17:53

0

Putting this answer so that hopefully it can come in google and help others.

expo command not found after using yarn global add expo-cli don't work in ubuntu 20.04

answered Nov 24 '21 at 17:53

Neel

428
1
4
12

Yarn global command not working

15 Answers15

! WARNING !

Option 2

Linked

Related