Yarn - How do I update each dependency in package.json to the latest version?

Question

I have a react app with deprecated dependencies. To make it work, I have to update the dependencies to their newer (but stable) versions.

As per this stakoverflow thread, to update dependencies in package.json to latest versions, npm-check-updates is the Best Option for npm. However, I'm using yarn for package management. Is there an equivalent of npm-check-updates in yarn. So that, I use a single package manager to manage my dependencies.

[npm-check-updates](https://github.com/raineorshine/npm-check-updates) is fully compatible with yarn. Just run `npx npm-check-updates` in your project directory. — Raine Revere, Jul 12 '22 at 14:49

Vahid Alimohamadi · Accepted Answer · 2021-03-27T20:40:57.140

243

yarn upgrade-interactive --latest

But you have to have a yarn.lock file before do it. If you are using npm, you must delete package-lock.json first. Then run yarn to create structure. After that you can do upgrade-interactive. Without that, yarn shows upgrade, but no changes and effects in package.json.

edited Mar 27 '21 at 20:40

answered Jun 30 '20 at 05:20

Vahid Alimohamadi

4,900
2
22
37

4

Clear your ```node_modules``` folder and ```yarn.lock``` , ```yarn-error.log``` files. Then try ```yarn --ignore-engines```. After successful instllations, try ```yarn upgrade-interactive --latest```. – Vahid Alimohamadi Jul 03 '20 at 06:30
8

If all of these had no success, then try ```yarn outdated``` and update packages directly manual in ```package.json``` one by one. You need to have relaxed mind before do that :) – Vahid Alimohamadi Jul 03 '20 at 06:34
1

Loved the `yarn outdated` as this seems more logical to do if got a long list of deps :) – just-be-weird Oct 17 '21 at 11:42
5

It's `yarn up` for the modern version of Yarn https://yarnpkg.com/cli/up – Daria Apr 21 '22 at 13:37
this inexplicably doesn't upgrade some packages. `npx npm-check-updates` seems to be the better solution. – codeflorist Sep 30 '22 at 13:55
'yarn upgrade-interactive --latest' Unknown Syntax Error: Unsupported option name ("--latest"). – bieboebap Nov 23 '22 at 11:31
Running this doesn't update my package.json – olawalejuwonm Jul 18 '23 at 17:56
Running this doesn't update my package.json – olawalejuwonm Jul 18 '23 at 17:57
@olawalejuwonm have you tried ```yarn ignore-engines``` at first to create the initial valid ```yarn.lock``` file before the upgrade? – Vahid Alimohamadi Jul 18 '23 at 18:43
@VahidAlimohamadi i already have a yarn.lock – olawalejuwonm Jul 18 '23 at 18:52
@olawalejuwonm remove ```node_modules```, ```yarn.lock``` and try ```yarn ignore-engines```. upgrade-interactive would work after that. – Vahid Alimohamadi Jul 19 '23 at 08:02
How can I store the upgraded versions in `package.json`? I see that the packages in `yarn.lock` got upgraded. – Qwerty Aug 19 '23 at 16:57

score 75 · Answer 2 · edited Aug 04 '21 at 23:15

75

You can upgrade a single package to the latest major version with this:

yarn upgrade <package-name> --latest

edited Aug 04 '21 at 23:15

Jeremy Caney

7,102
69
48
77

answered Oct 09 '20 at 13:33

Favour George

1,525
13
18

4

You want him to go one by one and list all his packages? – Davo Nov 24 '21 at 00:54
18

Sometimes you want to only update a single dependency. For updating the patch version (major.minor.patch), you can use e.g. yarn upgrade @1.1.x (use whatever major/minor version you have) – zmx Dec 14 '21 at 08:55
2

@zmx is the best answer in this page. Upgrading an entire dependency may end up in a rabbit hole, and unfortunately the other suggestions don't always work. – Miguel Mar 22 '22 at 21:49
6

This answer is wrong--this command does not update the package.json with the latest version. – wheeler Apr 23 '22 at 04:25
1

you can also use `--pattern=""` instead of `` – sam Sep 15 '22 at 14:28
This doesn't upgrade the major version. – wilmol May 22 '23 at 04:39
npx npm-check-updates works just fine – olawalejuwonm Jul 26 '23 at 09:57

score 54 · Answer 3 · edited Dec 27 '22 at 08:42

54

You can try this npm package yarn-upgrade-all. This package will remove every package in package.json and add it again which will update it to latest version.

installation:

npm install -g yarn-upgrade-all

usage: in your project directory run:

yarn-upgrade-all

edited Dec 27 '22 at 08:42

b3hr4d

4,012
1
11
24

answered Jul 08 '20 at 18:16

Ahmed Mokhtar

2,388
1
9
19

4

Thanks! Its a good option with only one caution. From official docs "Don't use yarn to install it on Windows because there is a bug https://github.com/yarnpkg/yarn/issues/2224" – DevLoverUmar Jul 08 '20 at 18:29
6

This package runs `yarn remove && yarn add` for all packages in `package.json` Too slow, but works! Shorter version: `npx yarn-upgrade-all` – Andrew Zolotarev Jan 26 '21 at 19:46
3

`yarn yarn-upgrade-all` didn't work for me but `npx yarn-upgrade-all` worked. Thanks @AndrewZolotarev – trkaplan May 29 '21 at 08:50
3

Running `npx yarn-upgrade-all` changed my `"vue": "^3.0.5"` dependency to `"vue": "^2.6.14"` which I did not expect. Obviously, this broke the build. – Glenn Jun 22 '21 at 13:59
2

`npx yarn-upgrade-all` – Guilherme Abacherli Nov 18 '21 at 16:22
He specifically said "newer (but *stable*) versions", which this does not - the result is similar to `yarn upgrade --latest`, which will also install breaking changes. I have not seen any command or tool that does what OP asked for. – mindplay.dk Jul 07 '22 at 09:07

score 19 · Answer 4 · edited Aug 04 '21 at 23:14

19

The one that worked for me is from a comment by @Andrew Zolotarev, which uses

npx yarn-upgrade-all

edited Aug 04 '21 at 23:14

Jeremy Caney

7,102
69
48
77

answered Aug 04 '21 at 22:09

Inventrohyder

311
2
3

2

For now I use `npx npm-upgrade`. I think it's better in usage for me. – Andrew Zolotarev Feb 11 '22 at 11:16

jmarceli · Answer 5 · 2022-07-03T12:20:01.200

17

With Yarn v2 and v3 (Berry)

You have to install appropriate plugin first with:

yarn plugin import interactive-tools

and then execute

yarn upgrade-interactive

Source: https://yarnpkg.com/cli/upgrade-interactive

edited Jul 03 '22 at 12:20

answered Jul 02 '22 at 17:36

jmarceli

19,102
6
69
67

Ali Fensome · Answer 6 · 2022-07-08T10:35:44.427

9

List outdated

yarn outdated

Upgrade all dependencies to latest

This will upgrade to the latest version, irrespective of if the package is stable or the versioning constraints between your packages.

yarn upgrade --latest

Yarn docs

edited Jul 08 '22 at 10:35

answered Apr 19 '22 at 16:23

Ali Fensome

440
4
7

This will install *unstable* versions - not what OP asked for. – mindplay.dk Jul 07 '22 at 09:11

score 9 · Answer 7 · answered Jul 12 '22 at 14:57

9

npm-check-updates is fully compatible with yarn. Just run npx npm-check-updates in your project directory.

npm-check-updates is a battle-tested, 8yr old library that just works. It offers interactive mode and doctor mode for automatically running tests and identifying broken upgrades.

Disclaimer: I am the main contributor of npm-check-updates.

Interactive + Group mode:

answered Jul 12 '22 at 14:57

Raine Revere

30,985
5
40
52

Why not: `yarn upgrade --latest` without needing to bother with an additional package installation – Eugene Jul 16 '22 at 21:49
@Eugene because no one understands what "yarn upgrade --latest" actually does. For example, I have "hardhat": "^2.9.5" in my package.json, and would expect yarn upgrade --latest to change that to 2.10.1. But no. (It's probably a flag somewhere, may caret? Don't know, don't care.) It did update other things though. ncu just does the sensible thing. – James Moore Aug 11 '22 at 16:37

score 4 · Answer 8 · answered Mar 25 '22 at 04:13

4

If you want to update packages with yarn and update the package.json accordingly,

Install syncyarnlock - yarn global add syncyarnlock
Update packages - yarn upgrade or yarn upgrade --latest
Sync updated versions of yarn.lock to package.json - syncyarnlock -s

answered Mar 25 '22 at 04:13

Arosha

1,311
2
16
22

note that you will need to run `yarn install` again as the last step - it won't do anything other than update `yarn.lock` again, but if you don't do this, `yarn` will complain later that the version constraints that were *used* when `yarn.lock` was generated are now out of date. – mindplay.dk Jul 07 '22 at 09:36

score 3 · Answer 9 · answered Feb 10 '22 at 02:51

In case you wanted to add the package to your package.json for development collaboration

yarn add yarn-upgrade-all -D

yarn yarn-upgrade-all

By the way, the package uses the command ( reinstall all packages again )

yarn install package1 package2 packageN

score 1 · Answer 10 · answered Feb 21 '23 at 21:12

1

Update dependencies to latest versions, using jq:

jq '.dependencies | keys | .[]' package.json | xargs yarn add

Update dev dependencies to latest versions:

jq '.devDependencies | keys | .[]' package.json | xargs yarn add --dev

answered Feb 21 '23 at 21:12

Pere

1,647
3
27
52

score 0 · Answer 11 · answered Aug 05 '22 at 13:00

0

For the latest versions of yarn (for me it's 3.2.2)

yarn up --interactive

For more details in the official docs.

answered Aug 05 '22 at 13:00

DevLoverUmar

11,809
11
68
98

1

I don't understand the design decisions in yarn up. For example, the latest hardhat version is 2.9.9. I have "hardhat": "^2.9.5" specified in package.json. You would expect yarn up --interactive would change 2.9.5 to 2.9.9, but instead it does nothing. The documentation talks about design decisions involving flags like caret, tilde, and exact; I didn't think it was worth bothering to figure out how those worked. ncu, on the other hand, does a useful thing in an obvious way. – James Moore Aug 11 '22 at 16:32
@JamesMoore you need a valid ```yarn.lock``` file before the upgrade operation. – Vahid Alimohamadi Oct 08 '22 at 21:33
@VahidAlimohamadi that just makes it worse. I'd expect "yarn up" to make changes to package.json whether or not there's a yarn.lock. Also, yarn.lock doesn't appear in the documentation for yarn up; that seems bad. – James Moore Oct 09 '22 at 00:59
1

@JamesMoore I'm not a YARN team member man! I just say it as a workaround! – Vahid Alimohamadi Oct 09 '22 at 07:32
This command does not relly work for me. I am using `yarn up --interactive "*"` – tmaier Jul 23 '23 at 07:03

score 0 · Answer 12 · answered Dec 15 '22 at 11:34

0

If none of the answers worked for you, try to install again:

yarn add {PACKAGENAME HERE}

it will overwrite the current version to the latest version available

answered Dec 15 '22 at 11:34

sFritsch09

424
4
10

score 0 · Answer 13 · answered Dec 20 '22 at 02:27

It can be done with --ignore-engines flag. So package installation will not fail due to an incompatible node version.

First run:

yarn --ignore-engines 
// This will install the older packages

And then:

yarn upgrade --ignore-engines 
// This will update packages to latest

Yarn - How do I update each dependency in package.json to the latest version?

13 Answers13

With Yarn v2 and v3 (Berry)

List outdated

Upgrade all dependencies to latest

Linked