Logo
Back

How can I update each dependency in package.json to the latest version?

When you want to update all (or many) of your dependencies in a Node.js project to their latest versions, there are several tools and methods you can use. The most common and convenient approach is to leverage the npm-check-updates (NCU) utility. Below, we’ll walk through how to install and use it, plus a few alternative strategies.

1. Using npm-check-updates (Recommended)

The npm-check-updates package scans your package.json and shows which dependencies can be upgraded to the newest versions (including major releases).

Steps

  1. Install npm-check-updates globally:

    npm install -g npm-check-updates

    Or install it locally in your project:

    npm install --save-dev npm-check-updates

  2. Check for Updates:

    ncu

    This command displays a list of dependencies and the versions they can be upgraded to.

  3. Upgrade package.json:

    ncu -u

    The -u (or --upgrade) flag updates your package.json file with the latest versions.

  4. Install Updated Dependencies:

    npm install

    or

    yarn install

    This will install the newly updated dependencies.

Example

$ ncu
Checking /path/to/package.json
[====================] 9/9 100%

 react  ^17.0.2  →  ^18.2.0

Run ncu -u to upgrade package.json

After running ncu -u, your package.json will reflect the changes (e.g., react might go from ^17.0.2 to ^18.2.0). Then run npm install.

2. Using the Built-In npm or yarn Commands

a) npm outdated

You can check which packages are outdated by running:

npm outdated

This displays current, wanted, and latest versions. However, npm outdated alone doesn’t automatically update your package.json.

b) npm update

npm update
  • By default, npm update updates packages to the wanted range specified in package.json (i.e., it respects ^ and ~). It doesn’t always install the latest major versions if they are out of your specified range.

c) Yarn’s upgrade

If using Yarn (v1):

yarn upgrade
  • This also respects your semver ranges.
  • You can force specific versions by editing package.json manually or using yarn upgrade <package>@latest.

Note: Both npm update and yarn upgrade don’t necessarily bump major versions outside the declared range. They’ll keep you within the constraints specified in your package.json.

3. Manually Editing package.json

For a small project, you can:

  1. Edit version numbers in package.json to ^latest or remove the version constraints entirely (not recommended for large projects).
  2. Then run npm install or yarn install.

This approach is more error-prone for large projects. Tools like npm-check-updates save you the hassle of manual edits.

4. Best Practices and Precautions

  1. Check for Breaking Changes

    • Jumping to the latest major version can introduce incompatibilities. Review release notes or changelogs.

  2. Incremental Upgrades

    • Sometimes upgrading everything at once can make debugging harder. Consider upgrading critical dependencies first, then others incrementally.

  3. Use Version Control

    • Before upgrading, commit your current code so you can easily revert if an update breaks something unexpectedly.

  4. Automated Testing

    • Ensure your project has tests or at least a manual testing process to confirm everything still works after upgrades.

Recommended Resources

Conclusion

  • npm-check-updates (NCU) is the most straightforward tool to check and upgrade your package.json dependencies to the latest versions in one go.
  • npm update or yarn upgrade respect semver constraints in your package.json, so they won’t necessarily push you to the newest major release.
  • Always be mindful of breaking changes when updating major versions, and use version control to revert if issues arise.

With a solid testing strategy and these tools at your disposal, you can keep your dependencies current without risking unexpected breakage in your Node.js projects.

CONTRIBUTOR
TechGrind