Yarn: `yarn global upgrade` needed? or just use `yarn global add ...` ?

[jokeyrhyme]

Do you want to request a _feature_ or report a _bug_?

feature ? really a question about a possible feature? :)

What is the current behavior?

We can yarn add blah and yarn upgrade

We can also yarn global add blah

But we can't yet yarn global upgrade. Is this something we should have?

Note that this is not for parity with npm, because npm --global update pretty much never had the expected behaviour, and its usage was discouraged as far as I can tell.

What is the expected behavior?

yarn global upgrade works its magic, and all globally installed packages are now their latest available versions

I do not think yarn itself should be upgraded, as we'll have yarn self-update for that

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

node --version

v6.7.0

yarn --version

0.15.1

uname -a

Darwin fulmen.local 16.1.0 Darwin Kernel Version 16.1.0: Mon Oct 3 14:03:15 PDT 2016; root:xnu-3789.21.3~20/RELEASE_X86_64 x86_64

[moimael]

Also I think that a yarn global outdated command is much needed too.

[adamsiwiec]

This could be dangerous and discouraged, but what about yarn global clean being added to the cli?

[lgh06]

I also wanna update a package globally installed...

[cchamberlain]

Not sure why this is necessary? Running lerna global add <package>@latest works fine for me and is inline with how local npm installs work when it comes to updates.

[turdiyev]

npm install -g yarn works only