v2.4.0-northbrook

Northbrook now does a few new things.

The packages field is no longer mandatory, if none is defined it defaults to the directory with your northbrook.json

The output is nicer or most things. Colors have been added to distinguish different parts of prompts and output.

Also a scripts section has been added that mirrors that of npm run can be used as nb run <scriptName>

// northbrook.json
{
  "scripts": {
    "test": "mocha -r buba/register"
  }
}

Very powerful when used in conjunction with extends. Since you can simply reuse commands by using a base configuration

When you runnb release --check it will go through the motions and tell you what release it plans to do, and what it would prepend to your changelog when not run in check mode.

nb exec supports running commands that require interactive input (prompts). So you could do nb exec -- nb commit for instance. (No good reason to, but it's possible)

When running nb release right before executing npm publish it will now run npm login for you.
It's quite often that you will need to change users to release specfic packages, and very easy to forget you need to. If you don't need this feature you can use the --skip-login flag.