How do I update devDependencies in NPM?

Question

npm update seems to just update the packages in dependencies, but what about devDependencies.

Right now you can install devDependencies by running npm install ., but this doesn't work for npm update .

Any ideas?

I just ran into the same thing. I'm surprised at this asymmetry between `npm install` and `npm update`. I worked around it by deleting my `node_modules` directory and then running `npm install` again, but it sure seems like there should be a better way. — Joe White, Apr 14 '12 at 02:01
I opened a [bug report](https://github.com/isaacs/npm/issues/2369) for this behavior. We'll see what happens. — Joe White, Apr 14 '12 at 12:21
This may be because the NPM devs thought that people would use `npm link` for doing dev environments. — Julian Knight, Jul 02 '12 at 10:58
Does this answer your question? [How to update each dependency in package.json to the latest version?](https://stackoverflow.com/questions/16073603/how-to-update-each-dependency-in-package-json-to-the-latest-version) — Henke, Feb 24 '22 at 12:34

deckerdev · Accepted Answer · 2017-07-18T16:50:34.947

185

To update package.json in addition to the local modules, run

npm update --save-dev

Alternatively, the same command to save time

npm update -D

You can view the full detail of update, or any command for that matter through

npm help <cmd>

edited Jul 18 '17 at 16:50

answered Jan 16 '14 at 23:08

deckerdev

2,766
2
21
23

32

`npm update -D` did not work for me, it didn't update anything. – AmazingDreams Jan 21 '16 at 11:25
43

Why is this marked as the correct answer when the question is not how to save updates to `package.json` but rather how to make `npm update` to update devDependencies? – Alejandro García Iglesias Apr 11 '16 at 21:18
@onalbi: it does not. Here's the [thread tracking the issue](https://npm.community/t/npm-update-doesnt-save-package-json/872/6?u=dandv). – Dan Dascalescu Sep 26 '18 at 03:03
3

`npm update --save-dev` works just fine for me. Using node `v12.11.0` and npm `v6.11.3` – Maxime Dupré Feb 11 '20 at 20:19
1

Nothing from the stated is working! (Downvoting). – JAN Mar 28 '21 at 12:56

score 66 · Answer 2 · answered Mar 14 '14 at 19:32

66

Install npm-check-updates (https://www.npmjs.org/package/npm-check-updates), then jump into your project folder and run:

npm-check-updates

And to update and save changes to your package.json file:

npm-check-updates -u

answered Mar 14 '14 at 19:32

Michael Thompson

4,181
1
29
24

`ncu` would be better than `npm-check-updates` to save typing. – Edric Jul 13 '18 at 15:18
@DimitriKopriwa there's a `-d` option for devDependencies only – Michael Thompson Dec 19 '18 at 15:06
2

ncu --dep dev -u; npm install – Kiruahxh Dec 20 '19 at 09:52
This may update vue dependencies to a higher version than the latest version that vue-cli supports. – Alex Wade May 13 '21 at 18:04

score 17 · Answer 3 · answered May 11 '20 at 23:24

17

These steps worked for me :

npm install -g npm-check-updates
ncu -u
npm update
npm install

answered May 11 '20 at 23:24

Alferd Nobel

3,185
2
30
35

2

Why we have to use third party thing for this kind of work? So weird. I could not make npm update change package.json – srknzl Mar 19 '21 at 18:02
3. is probably not needed, you can skip it. – Diego Ferri Apr 29 '21 at 08:28
step 4. is obviated by step 3. The response from @Daniel Danielecki does a better job of explaining what each of these steps actually does. https://stackoverflow.com/a/68375286/413538 – JamesWilson Mar 10 '22 at 03:33

score 11 · Answer 4 · answered Jul 14 '21 at 09:16

npm outdated - for an overview what's outdated
npm install -g npm-check-updates - as pointed correctly by Michael
ncu -u - it'll automatically update all dependencies (also dependencies, i.e., it's of course different than devDependencies) versions in package.json, without reinstalling it yet. It'll just change the "numbers" in package.json
npm update - actual dependencies installation
(Optional, depending by scenario) you might need to use the flag --force, or (new in NPM v7) --legacy-peer-deps to complete the process. You can read about difference between those 2 on What does npm install --legacy-peer-deps do exactly? When is it recommended / What's a potential use case?
(Optional) you can validate it using ncu -u and for correctly updated dependencies you should see the text All dependencies match the latest package versions :)

score 5 · Answer 5 · answered Oct 12 '13 at 17:37

5

This problem does no longer excise with the current version of NPM (1.3.11).

Update works fine with: npm update

answered Oct 12 '13 at 17:37

Chris Spiegl

345
3
8

3

Unfortunately, it does not. Here's the [thread tracking the issue](https://npm.community/t/npm-update-doesnt-save-package-json/872/6?u=dandv). – Dan Dascalescu Sep 26 '18 at 03:04

score 4 · Answer 6 · answered May 13 '15 at 11:05

4

If you are using outdated npm version it might be the problem. So before any other commands execute:

sudo npm install npm -g

or (if above doesn't work):

sudo npm update npm -g

Then relaunch the console (in order for changes to take effect). Now you can check your new npm --version and if it is up to date execute:

npm update

or (if you prefer):

npm update --save-dev

answered May 13 '15 at 11:05

jmarceli

19,102
6
69
67

Unfortunately, this doesn't work in npm 5. Here's the [thread tracking the issue](https://npm.community/t/npm-update-doesnt-save-package-json/872/6?u=dandv). – Dan Dascalescu Sep 26 '18 at 03:04

score 2 · Answer 7 · answered Nov 09 '13 at 14:35

I ran into the same problem as OP had, and found no solution, so I decided to write a Grunt plugin that will auto-update my devDependencies..

It's on Github, I'd love to get some input and collaborations in order to make it the best tool that NPM hasn't provided.

Basically it will auto-update your outdated development dependencies with a simple Grunt Task.

https://github.com/pgilad/grunt-dev-update

score 2 · Answer 8 · answered Jul 18 '17 at 11:46

2

What worked for me is installing individual dev dependencies like this

npm install react-test-renderer@15.6.1 --save --only=dev

answered Jul 18 '17 at 11:46

Varsha

29
6

`npm install package-name@version --save-dev` -> `only="dev"` is not correct – reydelo Dec 16 '22 at 11:04

score 2 · Answer 9 · answered Nov 17 '21 at 07:39

i found the answer onhttps://nodejs.dev/learn/update-all-the-nodejs-dependencies-to-their-latest-version and this is working for me for all the major release as well

npm install -g npm-check-updates
ncu -u
npm update

to check the outdated package use

npm outdated

score 1 · Answer 10 · answered Oct 07 '13 at 17:21

1

One (slow) way to do force the update, is to remove the node_modules directory, and then do npm install again.

This was a known bug of the npm update command, which has been fixed on the development branch of npm, see here: https://github.com/isaacs/npm/pull/3863

It should land on the latest stable version of npm pretty soon.

answered Oct 07 '13 at 17:21

Rick Deckard

1,239
1
11
10

1

In case of npm > v5 you would also need to remove `package-lock.json` to make this work, otherwise it will just install the versions listed in that lock file. – karfau Oct 10 '17 at 08:23
Also, this won't update `package.json` for you. Here's the [thread tracking the issue](https://npm.community/t/npm-update-doesnt-save-package-json/872/6?u=dandv). – Dan Dascalescu Sep 26 '18 at 03:05

How do I update devDependencies in NPM?

10 Answers10

Linked