Show outdated packages versions and upgrade all outdated

[MrEfrem]

Thank you for your awesome work. This release is very promising.
But it hasn't at least two important commands.
Yarn v1:
yarn outdated - show list outdated packages versions.
yarn upgrade - upgrade all minor versions of outdated packages.
I use it very often.

First I run yarn upgrade to update automatically all minor versions. Then I run yarn outdated and already manually update packages to major versions with changing my sources.
I think so workflow use the most part of people who use yarn or npm.
Why is it not implemented?
Even here @arcanis mentioned that outdated is the main command a year ago yet: #546 (comment)

[deini]

@MrEfrem have you tried upgrade-interactive ?

[MrEfrem]

Oh, yes. It works and what I wanted. Thank you very much. But I spent much time while I tried to find the same commands I used in npm and yarn v1.
Would be very good if you added link on this command in the migration article and also mentioned there that it replaces outdated and upgrade all packages.
And maybe it should be added to the Usage section: https://yarnpkg.com/getting-started/usage
because really those commands are very important.

[milesj]

@MrEfrem FWIW, upgrade-interactive has existed in v1 since inception.

[MrEfrem]

@milesj I hadn’t need to search it because those commands I mentioned above worked for me very well in both packages managers. And what do you mean yet? Because it was re-implemented we should wait at least the outdated command?

[jakst]

I don't think upgrade-interactive solves the same use case as outdated does.

In yarn-v1 I regularly use both commands - yarn outdated for a quick scan if there are any packages that need upgrade, and then a couple of rounds of yarn upgrade-interactive to progressively upgrade packages from "guaranteed to not break" to "will probably break something".

Here are three reasons why yarn outdated is still needed:

• It is easier to type than yarn upgrade-interactive which is nice for people like me who run yarn outdated several times a day.
• It does not capture terminal input and is therefore less abrupt than yarn upgrade-interactive. This behaviour also allows yarn outdated to be combined with other commands, like yarn outdated && yarn start.
• It does not show all packages, and is therefore faster to scan. (Why does the new upgrade-interactive show all packages by the way?)

[wesrice]

I just upgraded from Yarn v1 to v2. I am surprised that commands akin to yarn outdated and yarn upgrade do not exist. This issue is the only place that I've found addressing the topic, so I'll leave my use case here.

I regularly utilize yarn upgrade for minor and patch upgrades, then run a subsequent yarn outdated to see what major upgrades exist for my projects. I use this as a way of measuring technical debt with the thought that the more major upgrades that exist for my project, the harder it is going to be to maintain the project down the road. At work, I use this as a factor in vouching for feature prioritization. Without yarn upgrade and yarn outdated, I have a much more difficult time doing this.

Is there an expectation that voids like this in Yarn v2 should be filled via plugins?

[robclancy]

This is super weird :/

[danielkcz]

Oh my. So everyone is going to meet in this closed issue after painfully realizing that outdated doesn't work and docs don't mention any migration path. Same for the list and who knows what else. That's a rather sad approach :/

Also, the new upgrade-interactive is fairly confusing. It's not clear that the first column means no update will happen. And it's ugly as hell on Windows.

But I do like that it allows choosing upgrading minor or major. In the previous iteration, the --latest was somewhat cumbersome.

[robrichard]

Is there a non-interactive way to upgrade all packages that satisfy the current ranges in the package.json? We used to use yarn upgrade to do this.

[PutziSan]

Is there a non-interactive way to upgrade all packages that satisfy the current ranges in the package.json? We used to use yarn upgrade to do this.

Is this possible?

At the moment I find it very difficult to update my packages in a larger workspace. upgrade-interactive shows me about 100 packages (but only 20 at a time and I have to scroll via keyboard arrows), but most of them cannot be upgraded because there is no newer version. The visual selection is very tiring because the lines are very narrow and I often slip in the line. (maybe the UI is only on windows that bad, I don't know)

When I managed to select everything I want, there is often an error (net gone or the files are blocked by the ide), so that nothing is updated and I have to go through the process again.

[nicolabello]

@robrichard @PutziSan I think you are looking for https://yarnpkg.com/cli/up