yarn outdated global?

[rightaway]

I tried sudo yarn outdated --global-folder /usr/lib/node_modules but I get no output on the global modules installed in /usr/lib/node_modules. How can I report outdated global packages?

[justo]

I think the command would be yarn global outdated, but I agree that it should be added. yarn global upgrade has been added but there is no easy way to tell which packages are outdated without upgrading them all.

[guoliang]

You still have npm install even though you have yarn right? So why don't you simply use npm outdated -g

[eweap]

@guoliang Some yarn users (including myself) use a different folder than NPM for global packages (ex: /home/jonathan/.config/yarn/global) so npm outdated -g will not work

What I do when I need to know the list of global packages outdated: I go to /home/jonathan/.config/yarn/global (which contains a package.json file and yarn.lock who manage global packages) and I run yarn outdated in that folder.

I hope this will help while waiting for the yarn global outdated

[onehorsetown]

@eweap - Great idea. Thanks!

[eweap]

With the v0.23.2 release you can now run yarn global upgrade-interactive

[rightaway]

Seems to be a lot of interest in this one, any chance the developers would want this in yarn?

[ruchern-chong]

I just tried yarn global outdated today and it appears that this has not been implemented yet. Any updates on this?

[ateufel]

@ruchern yarn global upgrade-interactive works well, it does not just show outdated packages, you can even directly upgrade them. It only shows global packages installed with yarn though, but you can just npm uninstall -g and yarn global add them :)

[hardchor]

alternatively, you can

cd `yarn global dir`
yarn outdated

[yunti]

Would love this to be added for better consistency when using yarn. I keep coming up against this.