-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Show outdated packages versions and upgrade all outdated #749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@MrEfrem have you tried upgrade-interactive ? |
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 |
@MrEfrem FWIW, |
@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? |
I don't think upgrade-interactive solves the same use case as outdated does. In yarn-v1 I regularly use both commands - Here are three reasons why
|
I just upgraded from Yarn v1 to v2. I am surprised that commands akin to I regularly utilize Is there an expectation that voids like this in Yarn v2 should be filled via plugins? |
This is super weird :/ |
Oh my. So everyone is going to meet in this closed issue after painfully realizing that Also, the new But I do like that it allows choosing upgrading minor or major. In the previous iteration, the |
Is there a non-interactive way to upgrade all packages that satisfy the current ranges in the package.json? We used to use |
Is this possible? At the moment I find it very difficult to update my packages in a larger workspace. 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. |
@robrichard @PutziSan I think you are looking for https://yarnpkg.com/cli/up |
As far as I know yarn up only works with explicitly naming each dependency. |
You can use glob patterns in it, so for example |
Okay, thx @merceyz . |
For anyone following this thread looking for the You can find my plugin here: https://github.com/mskelton/yarn-plugin-outdated and it can be imported via: yarn plugin import https://mskelton.dev/yarn-outdated/v3 |
Is there a way i can get list of only outdated dependencies. |
I think the lack of replacement for This gap should be filled in officially (community plugins support are welcome too but having a built-in support is a must) Taking away things that worked well with no good enough replacement is a downgrade. |
@PikachuEXE I don't want to spark a big disagreement or debate, but let me say a few things in defense of Maël and the team. Yarn is an incredible tool that has grown and matured greatly since its inception and Yarn 2 was no exception. A redesigned core that allowed for faster iteration on features, support for community plugins, project level versioning for easier migration, and much more makes Yarn 2 a fantastic developer experience. While there are certainly some differences (like built in replacement for Yarn is not unique in this regard. webpack is extremely successful with it's plugin architecture where webpack maintains some official tools (e.g. webpack-dev-server), while allowing the community to build on the framework webpack has built. Many people probably don't realize that the heavily used Change is hard, and migrations are really hard. I get that. There was discussion before Yarn 2 was released about if it should be named something else since it was such a big change to Yarn. Ultimately, I feel that Maël and the team made the right decision, and the community has began to fill in some of the gaps that Yarn 2 left behind. P.S. |
I re-read the migration guide just to be sure. P.S. #1492 is opened for a year and I still don't see any response from dev. This is another blocking issue for my attempt to upgrade to yarn berry. |
@PikachuEXE I found the |
@PikachuEXE but if you really very want the outdated command check here a community plugin: https://yarnpkg.com/features/plugins |
@MrEfrem I have tried the outdated plugin briefly and it looks fine to me. (Though I already know its presence by reading the plugin authors comment above :) ) But I have tried
There are already many comments above describing what I am using I have also tried |
You can always use |
Thanks, this was a great tip. From here it's easy to replicate the old behaviour by adding the following to |
I just upgrade to Yarn Berry and I'm super confused about this. In my I need a command that does the same as It seems like what I can do as a workaround right now is delete |
@cdauth There is a recursive option for https://yarnpkg.com/cli/up#options-R%2C-recursive To use it, just add |
@mskelton Thank you, I can confirm that |
It seems that |
If you imagine the commands operate on a tree, by default they'll only run on the roots of these trees. The In the case of foreach it's a little special although it's loosely similar, I'd like to re-syntax the cli options to clarify those behaviors. |
if checking package versions for upgrades, its better to use this yarnpkg/berry#749 https://yarnpkg.com/cli/upgrade-interactive
My 2 cents after reading this long thread: |
I tried this and it didn't work as expected. It updated my Is there any command that does that? The only thing that has worked for me since upgrading to Yarn 2 is deleting the |
It seems to me like
|
@rudolfbyker Damn, I think you're right, based on the docs:
I just tested it and it did exactly what I wanted. Upgrade all packages within the constraints in Thank you for pointing this out! My only complaint now is why the command is so unintuitive. :) |
Is there a way to not upgrade major versions with With
Option 2 would be easier if |
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 runyarn 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
ornpm
.Why is it not implemented?
Even here @arcanis mentioned that
outdated
is the main command a year ago yet: #546 (comment)The text was updated successfully, but these errors were encountered: