JSPM

npm-check

Check for outdated, incorrect, and unused dependencies.

CLI

This is how you should use npm-check.

Install

$ npm install -g npm-check

Use

$ npm-check

The result should look like the screenshot, or something nice when your packages are all up-to-date and in use.

Options

$ npm-check --help

  Usage: npm-check [options]

  Options:

    -h, --help         output usage information
    -V, --version      output the version number
    -u, --update       Interactive update.
    -g, --global       Look at global modules.
    -s, --skip-unused  Skip check for unused packages.
    -p, --production   Ignore devDependencies.

-u, --update

Show an interactive UI for choosing which modules to update.

Automatically updates versions referenced in the package.json.

Based on recommendations from the npm team, npm-check only updates using npm install, not npm update. To avoid using more than one version of npm in one directory, npm-check will automatically install updated modules using the version of npm installed globally.

-g, --global

Check the versions of your globally installed packages.

Tip: Use npm-check -u -g to do a safe interactive update of global modules, including npm itself.

-s, --skip-unused

By default npm-check will let you know if any of your modules are not being used by looking at require statements in your code.

This option will skip that check.

This is enabled by default when using global or update.

-p, --production

By default npm-check will look at packages listed as dependencies and devDependencies.

This option will let it ignore outdated and unused checks for packages listed as devDependencies.

API

The API is here in case you want to wrap this with your CI toolset.

var npmCheck = require('npm-check');

npmCheck(options)
  .then(result);

npmCheck(options) returns promise

options

global boolean

• default is false

Use the globally installed packages. When true, the path is automatically set.

update boolean

• default is false

Interactive update.

skipUnused boolean

• default is false

Skip checking for unused packages.

ignoreDev boolean

• default is false

Ignore devDependencies.

path string

• default is cwd

Override where npm-check checks.

#####result

object of module names : data

data looks like this:

About the module

• moduleName: name of the module.
• homepage: url to the home page.

Versions

• latest: latest according to the registry.
• installed: version in node_modules.
• packageJson: version or range in package.json.
• devDependency: Is this a devDependency?
• usedInScripts: Is this used in the scripts section of package.json?
• mismatch: Is the version installed not match the range in package.json?
• semver_validRange: Is the package.json range valid?
• semver_valid: Is the installed version valid semver?
• easy_upgrade: Will using npm install upgrade the module?
• bump: What kind of bump is required to get the latest, such as patch, minor, major.
• unused: Is this module used in the code?

Inspiration

• npm outdated - awkward output, requires --depth=0 to be grokable.
• david - does not work with private registries.
• update-notifier - for single modules, not everything in package.json.
• depcheck - only part of the puzzle. npm-check uses depcheck.

About the Author

Hello fellow developer! My name is Dylan Greene. When not overwhelmed with my two kids I enjoy contributing to the open source community. I'm a tech lead at Opower. I lead a team using Grunt and Angular to build software that successfully helps people like us use less power. Not too long ago I co-created Doodle or Die, a hilarious web game with millions of doodles that won us Node Knockout for the "most fun" category. I'm dylang on Twitter and other places.

Some of my other Node projects:

This list was generated using anthology.

License

Copyright (c) 2014 Dylan Greene, contributors.

Released under the MIT license.

Screenshots are CC BY-SA (Attribution-ShareAlike).

Generated using grunt-readme with grunt-templates-dylang on Sunday, October 19, 2014.