npm-check-updates

npm-check-updates upgrades your package.json dependencies to the latest versions, ignoring specified versions.

• maintains existing semantic versioning policies, i.e. "react": "^17.0.2" to "react": "^18.3.1".
• only modifies package.json file. Run npm install to update your installed packages and package-lock.json.
• sensible defaults, but highly customizable
• compatible with npm, yarn, pnpm, deno, and bun
• CLI and module usage

$${\color{red}Red}$$ major upgrade (and all major version zero)
$${\color{cyan}Cyan}$$ minor upgrade
$${\color{green}Green}$$ patch upgrade

Installation

Install globally to use npm-check-updates or the shorter ncu:

1npm install -g npm-check-updates

Or run with npx (only the long form is supported):

1npx npm-check-updates

Usage

Check the latest versions of all project dependencies:

1$ ncu
2Checking package.json
3[====================] 5/5 100%
4
5 eslint             7.32.0  →    8.0.0
6 prettier           ^2.7.1  →   ^3.0.0
7 svelte            ^3.48.0  →  ^3.51.0
8 typescript         >3.0.0  →   >4.0.0
9 untildify          <4.0.0  →   ^4.0.0
10 webpack               4.x  →      5.x
11
12Run ncu -u to upgrade package.json

Upgrade a project's package file:

Make sure your package file is in version control and all changes have been committed. This will overwrite your package file.

1$ ncu -u
2Upgrading package.json
3[====================] 1/1 100%
4
5 express           4.12.x  →   4.13.x
6
7Run npm install to install new versions.
8
9$ npm install      # update installed packages and package-lock.json

Check global packages:

1ncu -g

Interactive Mode

Choose which packages to update in interactive mode:

1ncu --interactive
2ncu -i

Combine with --format group for a truly luxe experience:

Filter packages

Filter packages using the --filter option or adding additional cli arguments:

1# upgrade only mocha
2ncu mocha
3ncu -f mocha
4ncu --filter mocha
5
6# upgrade only chalk, mocha, and react
7ncu chalk mocha react
8ncu chalk, mocha, react
9ncu -f "chalk mocha react"

Filter with wildcards or regex:

1# upgrade packages that start with "react-"
2ncu react-*
3ncu "/^react-.*$/"

Exclude specific packages with the --reject option or prefixing a filter with !. Supports strings, wildcards, globs, comma-or-space-delimited lists, and regex:

1# upgrade everything except nodemon
2ncu \!nodemon
3ncu -x nodemon
4ncu --reject nodemon
5
6# upgrade packages that do not start with "react-".
7ncu \!react-*
8ncu '/^(?!react-).*$/' # mac/linux
9ncu "/^(?!react-).*$/" # windows

Advanced filters: filter, filterResults, filterVersion

How dependency updates are determined

• Direct dependencies are updated to the latest stable version:
  • 2.0.1 → 2.2.0
  • 1.2 → 1.3
  • 0.1.0 → 1.0.1
• Range operators are preserved and the version is updated:
  • ^1.2.0 → ^2.0.0
  • 1.x → 2.x
  • >0.2.0 → >0.3.0
• "Less than" is replaced with a wildcard:
  • <2.0.0 → ^3.0.0
  • 1.0.0 < 2.0.0 → ^3.0.0
• "Any version" is preserved:
  • * → *
• Prerelease versions are ignored by default.
  • Use --pre to include prerelease versions (e.g. alpha, beta, build1235)
• Choose what level to upgrade to:
  • With --target semver, update according to your specified semver version ranges:
    • ^1.1.0 → ^1.9.99
  • With --target minor, strictly update the patch and minor versions (including major version zero):
    • 0.1.0 → 0.2.1
  • With --target patch, strictly update the patch version (including major version zero):
    • 0.1.0 → 0.1.2
  • With --target @next, update to the version published on the next tag:
    • 0.1.0 -> 0.1.1-next.1

Options

Options are merged with the following precedence:

1. Command line options
2. Local Config File (current working directory)
3. Project Config File (next to package.json)
4. User Config File ($HOME)

Options that take no arguments can be negated by prefixing them with --no-, e.g. --no-peer.

Advanced Options

Some options have advanced usage, or allow per-package values by specifying a function in your .ncurc.js file.

Run ncu --help [OPTION] to view advanced help for a specific option, or see below:

doctor

Usage:

ncu --doctor -u
ncu --no-doctor
ncu -du

Iteratively installs upgrades and runs your project's tests to identify breaking upgrades. Reverts broken upgrades and updates package.json with working upgrades.

Requires -u to execute (modifies your package file, lock file, and node_modules)

To be more precise:

1. Runs npm install and npm test to ensure tests are currently passing.
2. Runs ncu -u to optimistically upgrade all dependencies.
3. If tests pass, hurray!
4. If tests fail, restores package file and lock file.
5. For each dependency, install upgrade and run tests.
6. Prints broken upgrades with test error.
7. Saves working upgrades to package.json.

Additional options:

Example:

$ ncu --doctor -u
Running tests before upgrading
npm install
npm run test
Upgrading all dependencies and re-running tests
ncu -u
npm install
npm run test
Tests failed
Identifying broken dependencies
npm install
npm install --no-save react@16.0.0
npm run test
  ✓ react 15.0.0 → 16.0.0
npm install --no-save react-redux@7.0.0
npm run test
  ✗ react-redux 6.0.0 → 7.0.0

/projects/myproject/test.js:13
  throw new Error('Test failed!')
  ^

npm install --no-save react-dnd@11.1.3
npm run test
  ✓ react-dnd 10.0.0 → 11.1.3
Saving partially upgraded package.json

filter

Usage:

ncu --filter [p]
ncu -f [p]

Include only package names matching the given string, wildcard, glob, comma-or-space-delimited list, /regex/, or predicate function. Only included packages will be checked with --peer.

--filter runs before new versions are fetched, in contrast to --filterResults which runs after.

You can also specify a custom function in your .ncurc.js file, or when importing npm-check-updates as a module.

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

1/**
2  @param name     The name of the dependency.
3  @param semver   A parsed Semver array of the current version.
4    (See: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring)
5  @returns        True if the package should be included, false if it should be excluded.
6*/
7filter: (name, semver) => {
8  if (name.startsWith('@myorg/')) {
9    return false
10  }
11  return true
12}

filterResults

Filters results based on a user provided predicate function after fetching new versions.

filterResults runs after new versions are fetched, in contrast to filter, reject, filterVersion, and rejectVersion, which run before. This allows you to exclude upgrades with filterResults based on how the version has changed (e.g. a major version change).

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

1/** Exclude major version updates. Note this could also be achieved with --target semver.
2  @param {string} packageName               The name of the dependency.
3  @param {string} current                   Current version declaration (may be a range).
4  @param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be a range).
5  @param {string} upgraded                  Upgraded version.
6  @param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
7  @returns {boolean}                        Return true if the upgrade should be kept, otherwise it will be ignored.
8*/
9filterResults: (packageName, { current, currentVersionSemver, upgraded, upgradedVersionSemver }) => {
10  const currentMajor = parseInt(currentVersionSemver[0]?.major, 10)
11  const upgradedMajor = parseInt(upgradedVersionSemver?.major, 10)
12  if (currentMajor && upgradedMajor) {
13    return currentMajor >= upgradedMajor
14  }
15  return true
16}

For the SemVer type definition, see: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring

filterVersion

Usage:

ncu --filterVersion [p]

Include only versions matching the given string, wildcard, glob, comma-or-space-delimited list, /regex/, or predicate function.

--filterVersion runs before new versions are fetched, in contrast to --filterResults which runs after.

You can also specify a custom function in your .ncurc.js file, or when importing npm-check-updates as a module.

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions. This function is an alias for the filter option function.

1/**
2  @param name     The name of the dependency.
3  @param semver   A parsed Semver array of the current version.
4    (See: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring)
5  @returns        True if the package should be included, false if it should be excluded.
6*/
7filterVersion: (name, semver) => {
8  if (name.startsWith('@myorg/') && parseInt(semver[0]?.major) > 5) {
9    return false
10  }
11  return true
12}

format

Usage:

ncu --format [value]

Modify the output formatting or show additional information. Specify one or more comma-delimited values.

groupFunction

Customize how packages are divided into groups when using --format group.

Only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

1/**
2  @param name             The name of the dependency.
3  @param defaultGroup     The predefined group name which will be used by default.
4  @param currentSpec      The current version range in your package.json.
5  @param upgradedSpec     The upgraded version range that will be written to your package.json.
6  @param upgradedVersion  The upgraded version number returned by the registry.
7  @returns                A predefined group name ('major' | 'minor' | 'patch' | 'majorVersionZero' | 'none') or a custom string to create your own group.
8*/
9groupFunction: (name, defaultGroup, currentSpec, upgradedSpec, upgradedVersion) => {
10  if (name === 'typescript' && defaultGroup === 'minor') {
11    return 'major'
12  }
13  if (name.startsWith('@myorg/')) {
14    return 'My Org'
15  }
16  return defaultGroup
17}

install

Usage:

ncu --install [value]

Default: prompt

Control the auto-install behavior.

packageManager

Usage:

ncu --packageManager [s]
ncu -p [s]

Specifies the package manager to use when looking up versions.

peer

Usage:

ncu --peer
ncu --no-peer

Check peer dependencies of installed packages and filter updates to compatible versions.

Example:

The following example demonstrates how --peer works, and how it uses peer dependencies from upgraded modules.

The package ncu-test-peer-update has two versions published:

• 1.0.0 has peer dependency "ncu-test-return-version": "1.0.x"
• 1.1.0 has peer dependency "ncu-test-return-version": "1.1.x"

Our test app has the following dependencies:

"ncu-test-peer-update": "1.0.0",
"ncu-test-return-version": "1.0.0"

The latest versions of these packages are:

"ncu-test-peer-update": "1.1.0",
"ncu-test-return-version": "2.0.0"

With --peer:

ncu upgrades packages to the highest version that still adheres to the peer dependency constraints:

ncu-test-peer-update     1.0.0  →  1.1.0
ncu-test-return-version  1.0.0  →  1.1.0

Without --peer:

As a comparison: without using the --peer option, ncu will suggest the latest versions, ignoring peer dependencies:

ncu-test-peer-update     1.0.0  →  1.1.0
ncu-test-return-version  1.0.0  →  2.0.0

registryType

Usage:

ncu --registryType [type]

Specify whether --registry refers to a full npm registry or a simple JSON file.

// local file
$ ncu --registryType json --registry ./registry.json

// url
$ ncu --registryType json --registry https://api.mydomain/registry.json

// you can omit --registryType when the registry ends in .json
$ ncu --registry ./registry.json
$ ncu --registry https://api.mydomain/registry.json

{
  "prettier": "2.7.1",
  "typescript": "4.7.4"
}

reject

Usage:

ncu --reject [p]
ncu -x [p]

The inverse of --filter. Exclude package names matching the given string, wildcard, glob, comma-or-space-delimited list, /regex/, or predicate function. This will also exclude them from the --peer check.

--reject runs before new versions are fetched, in contrast to --filterResults which runs after.

You can also specify a custom function in your .ncurc.js file, or when importing npm-check-updates as a module.

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

1/**
2  @param name     The name of the dependency.
3  @param semver   A parsed Semver array of the current version.
4    (See: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring)
5  @returns        True if the package should be excluded, false if it should be included.
6*/
7reject: (name, semver) => {
8  if (name.startsWith('@myorg/')) {
9    return true
10  }
11  return false
12}

rejectVersion

Usage:

ncu --rejectVersion [p]

The inverse of --filterVersion. Exclude versions matching the given string, wildcard, glob, comma-or-space-delimited list, /regex/, or predicate function.

--rejectVersion runs before new versions are fetched, in contrast to --filterResults which runs after.

You can also specify a custom function in your .ncurc.js file, or when importing npm-check-updates as a module.

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions. This function is an alias for the reject option function.

1/**
2  @param name     The name of the dependency.
3  @param semver   A parsed Semver array of the current version.
4    (See: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring)
5  @returns        True if the package should be excluded, false if it should be included.
6*/
7rejectVersion: (name, semver) => {
8  if (name.startsWith('@myorg/') && parseInt(semver[0]?.major) > 5) {
9    return true
10  }
11  return false
12}

target

Usage:

ncu --target [value]
ncu -t [value]

Determines the version to upgrade to. (default: "latest")

e.g.

ncu --target semver

You can also specify a custom function in your .ncurc.js file, or when importing npm-check-updates as a module.

:warning: The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

1/** Upgrade major version zero to the next minor version, and everything else to latest.
2  @param name     The name of the dependency.
3  @param semver   A parsed Semver object of the upgraded version.
4    (See: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring)
5  @returns        One of the valid target values (specified in the table above).
6*/
7target: (name, semver) => {
8  if (parseInt(semver[0]?.major) === '0') return 'minor'
9  return 'latest'
10}

Config File

Add a .ncurc.{json,yml,js,cjs} file to your project directory to specify configuration information.

For example, .ncurc.json:

1{
2  "upgrade": true,
3  "filter": "svelte",
4  "reject": ["@types/estree", "ts-node"]
5}

Options are merged with the following precedence:

1. Command line options
2. Local Config File (current working directory)
3. Project Config File (next to package.json)
4. User Config File ($HOME)

You can also specify a custom config file name or path using the --configFileName or --configFilePath command line options.

Config Functions

Some options offer more advanced configuration using a function definition. These include filter, filterVersion, filterResults, reject, rejectVersion, and groupFunction. To define an options function, convert the config file to a JS file by adding the .js extension and setting module.exports:

For example, .ncurc.js:

1module.exports = {
2  upgrade: true,
3  filter: name => name.startsWith('@myorg/'),
4}

JSON Schema

If you write .ncurc config files using json or yaml, you can add the JSON Schema to your IDE settings for completions.

e.g. for VS Code:

1  "json.schemas": [
2    {
3      "fileMatch": [
4        ".ncurc",
5        ".ncurc.json",
6      ],
7      "url": "https://raw.githubusercontent.com/raineorshine/npm-check-updates/main/src/types/RunOptions.json"
8    }
9  ],
10  "yaml.schemas": {
11    "https://raw.githubusercontent.com/raineorshine/npm-check-updates/main/src/types/RunOptions.json": [
12        ".ncurc.yml",
13    ]
14  },

Module/Programmatic Usage

npm-check-updates can be imported as a module:

1import ncu from 'npm-check-updates'
2
3const upgraded = await ncu.run({
4  // Pass any cli option
5  packageFile: '../package.json',
6  upgrade: true,
7  // Defaults:
8  // jsonUpgraded: true,
9  // silent: true,
10})
11
12console.log(upgraded) // { "mypackage": "^2.0.0", ... }

Contributing

Contributions are happily accepted. I respond to all PR's and can offer guidance on where to make changes. For contributing tips see CONTRIBUTING.md.

Problems?

File an issue. Please search existing issues first.