dep-ranger

dep-ranger

Cause if you don't keep up to date your dependencies you're a bad guy.

Installation

npm i dep-ranger

Usage

dep-ranger

Why?

Updating dependencies is hard, and it's even harder if you don't do it often.

Why not simply updating everything and be done with it?

We can divide dependencies in two categories:

• to keep updated: always update as soon as a new version is out

  • examples: tcomb, lodash

• to keep outdated: never update carelessly. Requires some discussion and agreement within the team.

  • examples: react, babel

If there are outdated or uncategorized dependencies the tool exit with an error.

The solution

dep-ranger runs npm outdated and notifies you if it finds dependencies belonging to the out-of-date group.

You can run this tool on your CI servers and always be in control of what dependencies are being left behind, with the flexibility of specifying what you don't care about.

Configuration

dep-ranger read dependencies configuration from .deprangerrc. You can define your toKeepOutdated deps as String or Object with name and reason key. The purpose of the reason key is to share why the dep shouldn't be updated across the team.

A valid .deprangerrc should look like this:

{
  "toKeepUpdated": ["react", "lodash"],
  "toKeepOutdated": [
    {
      "name": "babel",
      "reason": "Babel ^6 dropped support for decorators"
    },
    "eslint"
  ]
}