CODEWITHSUNDEEP
node.jsnpmnode-modulesnpm-installnpm-update
Samson
Samson

Reputation: 1898

How to update package.json to latest version of each package?

Before you flag it as duplicate, I have searched for the similar questions and none of them helped me.

Currently this is what I have tried:

  1. Delete package-lock.json file.
  2. Delete node_modules.
  3. Run npm update
  4. Run npm install

This would always allow me to install the latest (minor) version of the packages in node_modules, and update the package-lock.json file. However, the package.json file does not update.

For example, my moment is package.json is stated as "moment": "^2.27.0". After running above steps, package-lock.json will update to "moment": { "version": "2.29.1", ...} But package.json will still be "moment": "^2.27.0".

What is the correct way to do this? Running npm install moment manually updates the package.json to become "moment": "^2.29.1" but its quite absurd if I have to run npm install for every single dependency?

Edit Thanks to the selected answer, I realised that I do not actually need to update my package.json, as it shows compatible version, not exact version.

Upvotes: 36

Views: 67634

Answers (6)

Artur Vieira
Artur Vieira

Reputation: 4769

Use yarn, npm i -g yarn yarn install For getting up and running quickly.

Upvotes: 0

RayT
RayT

Reputation: 1

Consider running the npm audit, it should update and install the new version and update the package.json dependencies.

To address issues that do not require attention, run:

npm audit fix

To address all issues (including breaking changes), run:

npm audit fix --force

npm-audit Synopsis

Upvotes: -1

Sámal Rasmussen
Sámal Rasmussen

Reputation: 3515

There is an npm package called npm-check-updates that does this.

Using npx:

npx npm-check-updates -u
npm i

Or install globally first:

npm i -g npm-check-updates
ncu -u
npm i

Upvotes: 6

Daniel Alder
Daniel Alder

Reputation: 5382

How about

npm upgrade -S

-S stands for --save

Upvotes: 2

QT-1
QT-1

Reputation: 996

npm outdated lists all packages that can be updated with the current, wanted and latest version numbers.

  • current is the currently installed version
  • wanted is the last minor version update
  • latest is the latest major version update

To update all packages to latest just do:

npm outdated | awk 'NR>1 {print $1"@"$4}' | xargs npm install

which simply calls npm install with the latest version of each outdated package.

If you are using Windows Powershell, add --% after awk to prevent syntax errors:

npm outdated | awk --% 'NR>1 {print $1"@"$4}' | xargs npm install

It is highly recommended to check the resulting changes to your packages.json file just to make sure all changes are as expected.

Upvotes: 24

Hoto Cocoa
Hoto Cocoa

Reputation: 517

package.json will not updated by npm install. That contains about dependencies and compatible version list.

"moment": "^2.27.0" meaning allowed moment version: 2.27.0 <= version < 3.0.0, not allowed moment version = 2.27.0. So when you run npm install, npm will install the latest version of major version 2(In your case, 2.29.1), But package.json will not updated by that command. Because It not contains installed version, It contains compatible version.

However, npm install moment command do install the latest version of moment, So package.json updated the latest version, because "^2.27.0" is lower than "^2.29.1".

Anyway, If you want to update your package.json, You can use npm-check-updates (a.k.a. ncu). See this answer. If you not want running ncu, You can use "latest"(Example: "moment": "latest") to install the latest version anytime.

Upvotes: 18

Related Questions