commit | 35982a557a61ef04bb2ff66302dfe29be2e78fea | [log] [tgz] |
---|---|---|
author | Robert Kowalski <rok@kowalski.gd> | Sun Jul 12 14:00:00 2015 +0200 |
committer | Robert Kowalski <rok@kowalski.gd> | Sun Jul 12 14:00:00 2015 +0200 |
tree | b63842d249137a6dce8866a7b60dd4f4538945d9 | |
parent | 1f09715ccf49bfb203499c571d0cef1cd865a6f8 [diff] |
describe why we check in production modules
nmo
is a cli tool to manage CouchDB clusters and nodes.
npm install -g nmo
It is written in ES6 and is using promises and generators for control flow. We are aiming for 100% test coverage.
Production dependencies are checked in for multiple reasons:
bundledDependencies
in the package.json
file and npm just downloads one tarballnmo
still works for new installs