Your current version of Yarn is out of date "npm upgrade --global yarn" should be "npm install --global yarn"

[crucialfelix]

Current yarn: 0.19.1

bug

What is the current behavior?

The "yarn is out of date" message posts an npm command. This command doesn't succeed in updating yarn.

warning Your current version of Yarn is out of date. The latest version is "0.21.3" while you're on "0.19.1".
info To upgrade, run the following command:
$ npm upgrade --global yarn

But this command doesn't do it. yarn remains at 0.19.1

If the current behavior is a bug, please provide the steps to reproduce.

data-projector ❯ which yarn
/Users/crucial/.nvm/versions/node/v6.9.1/bin/yarn
data-projector ❯ npm upgrade --global yarn
data-projector ❯ yarn --version
0.19.1

data-projector ❯ npm --version
3.10.8

The npm command that works is install:

npm install --global yarn

yarn --version
0.21.3

data-projector ❯ npm install --global yarn
/Users/crucial/.nvm/versions/node/v6.9.1/bin/yarn -> /Users/crucial/.nvm/versions/node/v6.9.1/lib/node_modules/yarn/bin/yarn.js
/Users/crucial/.nvm/versions/node/v6.9.1/bin/yarnpkg -> /Users/crucial/.nvm/versions/node/v6.9.1/lib/node_modules/yarn/bin/yarn.js
- once@1.3.3 node_modules/yarn/node_modules/end-of-stream/node_modules/once
- exit-hook@1.1.1 node_modules/yarn/node_modules/exit-hook
- supports-color@0.2.0 node_modules/yarn/node_modules/gauge/node_modules/supports-color
- generate-function@2.0.0 node_modules/yarn/node_modules/generate-function
- is-finite@1.0.2 node_modules/yarn/node_modules/is-finite
- is-property@1.0.2 node_modules/yarn/node_modules/is-property
- generate-object-property@1.2.0 node_modules/yarn/node_modules/generate-object-property
- is-utf8@0.2.1 node_modules/yarn/node_modules/is-utf8
- jsonpointer@4.0.1 node_modules/yarn/node_modules/jsonpointer
- is-my-json-valid@2.15.0 node_modules/yarn/node_modules/is-my-json-valid
- os-shim@0.1.3 node_modules/yarn/node_modules/os-shim
- pinkie@2.0.4 node_modules/yarn/node_modules/pinkie
- pinkie-promise@2.0.1 node_modules/yarn/node_modules/pinkie-promise
- repeating@2.0.1 node_modules/yarn/node_modules/repeating
- typedarray@0.0.6 node_modules/yarn/node_modules/typedarray
- concat-stream@1.6.0 node_modules/yarn/node_modules/concat-stream
- spawn-sync@1.0.15 node_modules/yarn/node_modules/spawn-sync
- diff@2.2.3 node_modules/yarn/node_modules/diff
- user-home@2.0.0 node_modules/yarn/node_modules/user-home
/Users/crucial/.nvm/versions/node/v6.9.1/lib
└─┬ yarn@0.21.3

...

data-projector ❯ yarn --version
0.21.3

Now I know this sounds like an npm bug, certainly not a yarn bug.
According to npm docs it should be upgrade.

What is the expected behavior?

This:

yarn/src/cli/commands/install.js

Line 93 in 24199a0

if (YARN_INSTALL_METHOD === 'npm') {

should say:

return 'npm install --global yarn';

But honestly I'm not sure.

Please mention your node.js, yarn and operating system version.

Node 6.9.1
npm 3.10.8
OS X el capitain

[crucialfelix]

I'm closing this because it must be an npm bug. The command posted should be what npm documentation suggests.

[wsfuller]

There's a bit of a discussion on this on #1139 that ties into other issues.

npm install -g yarn solved the issue for me when nothing happened running npm update --global yarn.

Curious as to why there is a prompt for npm update --global yarn when the command doesn't do anything. And Yarn self-update is currently not available. Feels like there aren't any viable options other than doing an install.

[adamreisnz]

npm install -g yarn is the only thing that works. The message should be updated, even though upgrade should work, it clearly doesn't.

[XaserAcheron]

+1 for changing the help text to npm install -g yarn. Some thoughts on why:

Though this indeed is technically an npm bug, the relevant GitHub issue ( npm/npm#11534 ) has fallen victim to their new auto-close policy. Even if this was sneakily fixed at some point anyway, yarn users are now dependent on npm being up to date in order to ensure yarn's suggestion works, which is a weird pseudo-dependency.

In an ideal world, this would be fixed npm-side and the point would be moot, but I'd rather see yarn give consistently helpful documentation rather than rely on behavior of the tool it's meant to replace.

[adamreisnz]

Is there a particular reason by the way why we can't use yarn to upgrade yarn?

[crucialfelix]

I've installed yarn with brew now (OS X). Then it is available with any version of node I have active (I use nvm). Otherwise you have to install yarn in each node version global.

brew upgrade yarn

[adamreisnz]

I use n instead of nvm and never have had to reinstall it globally for a new version of Node (OS X too).

…

On Tue, Jun 27, 2017, 21:13 Chris Sattinger ***@***.***> wrote: I've installed yarn with brew now (OS X). Then it is available with any version of node I have active (I use nvm). Otherwise you have to install yarn in each node version global. brew upgrade yarn — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3042 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAd8QgK_Wz1jQpWoCIYD1LjoDKd0ipojks5sIMe6gaJpZM4MzyBN> .

[M-ZubairAhmed]

I too faced the same warning.
I looked into api docs for upgrading the issue. But i ended up following the tutorial for installing yarn and installed it again. It upgraded my yarn and the above warning didnt show up when i ran the command(which was yarn install for my repo) again.

[BirkhoffLee]

I encountered the same thing today, but the command is quite different :

warning Your current version of Yarn is out of date. The latest version is "1.0.2" while you're on "0.19.1".
info To upgrade, run the following command:
$ curl -o- -L https://yarnpkg.com/install.sh | bash

The command doesn't work either, unfortunately.

[adamreisnz]

I noticed that too. Really don't know what's wrong with npm i -g yarn

…

On Thu, Sep 21, 2017, 12:14 Birkhoff Lee ***@***.***> wrote: I encountered the same thing today, but the command is quite different : warning Your current version of Yarn is out of date. The latest version is "1.0.2" while you're on "0.19.1". info To upgrade, run the following command: $ curl -o- -L https://yarnpkg.com/install.sh | bash The command doesn't work either, unfortunately. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3042 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAd8Qv2wDTxmBS37d7cfuKageRDEy6eOks5skapUgaJpZM4MzyBN> .

[BYK]

@BirkhoffLee that should work actually. What's the error you are getting?

[BirkhoffLee]

Didn’t get any error or warnings. Everything looks fine but it just don’t work.

…

On Sep 21, 2017, 9:14 PM +0800, Burak Yiğit Kaya ***@***.***>, wrote: @BirkhoffLee that should work actually. What's the error you are getting? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[arcanis]

@BirkhoffLee The command displayed changes depending on how you've installed Yarn, so a different command isn't unusual.

[timhc22]

On Mac npm install -g yarn didn't upgrade yarn for me, but then I noticed that I already had it installed with homebrew so uninstalled from there and then ln -s ~/.nvm/versions/node/v6.11.0/bin/yarn /usr/local/bin/yarn. I had stopped using it, but needed to reuse for a library which was using it.

[konekoya]

Not sure if this will help anyone? I'm on macOS.
For people who have installed yarn with shell script like mentioning in here
And wanted to upgrade yarn with npm. You first need to rm -rf .yarn/ dir and then install yarn again with npm install -g yarn. Otherwise, you won't be able to use the newly installed yarn in your CLI. It will keep using the old one that you've installed with shell script.

[vijaychouhan-rails]

When I did run npm install -g yarn
then I got the deprecated warning and it did nothing

npm WARN deprecated yarn@1.3.2: It is recommended to install Yarn using the native installation method for your environment.

So I fixed it for:
1) On Debian or Ubuntu Linux, you can install Yarn via our Debian package repository. You will first need to configure the repository:

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list

2) sudo apt-get update && sudo apt-get install yarn

Now my installed yarn version is updated

[rmariuzzo]

What helped me was:

1. brew uninstall --force yarn.
2. rm -rf ~/.yarn.
3. npm install --global yarn

😎

[javadoug]

brew uninstall --force yarn
rm -rf ~/.yarn
# follow instructions here https://yarnpkg.com/en/docs/install
# on macOS --without-node bc I use nvm
brew install yarn --without-node

[Mark-A-A]

For those with Homebrew: brew upgrade yarn worked just fine

[s-h-a-d-o-w]

It's nice and all that there are so many workarounds for Mac users but... surely, I'm not the only Windows user? curl doesn't exactly do anything there...

What's the problem with npm install -g yarn? Why was that not used for the warning instead of curl?

[pstanton]

I can't update yarn by npm update --global yarn or npm install --global yarn

When I run the above it says 1.6.0 installed, however if i then run yarn --version it is stuck on 1.3.2.

I can't remember how I installed yarn to begin with.

(windows)

** UPDATE **

i had used choco, so choco upgrade yarn in an elevated shell worked for me

[Rolando-Barbella]

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

[gabrielguita]

What helped me was:

1. brew uninstall --force yarn.
2. rm -rf ~/.yarn.
3. npm install --global yarn

😎

This worked like a charm, cheers man!

[brandonros]

Somebody needs to publish 1.15.2 to npm. https://www.npmjs.com/package/yarn It's showing 1.13.0 while stable on http://yarnpkg.com is 1.15.2

[nhustak]

Just an FYI for anyone else running into this issue. It ended up I had apparently installed Yarn through a windows installer. It was finding this one first. I uninstalled it windows via Programs and Features and it then picked up the new one.