API: Customers

Lead Maintainer Shaun Berryman

##Installation: Install packages

npm install

Engines:

Minimum versions

{
    "node": ">=4",
    "npm": ">=3.3.0"
}

##Usage:

Debugging the application (this uses nodemon to monitor for file changes and automatically re-run the script)

npm run debug

##Testing:

Basic command line testing

npm test

Build coverage.html use lab html reporter

make test-cov-html

Automatically run make test-cov-html when file(s) change (this uses nodemon to monitor for file changes and automatically re-run the script)

npm run test-watch

Sending code coverage data to coveralls (you shouldn't need to do this as codeship handles it as part of its build)

npm run coveralls

Contributing

I generally don't accept pull requests that are untested, or break the build, because I'd like to keep the quality high (this is a coverage tool afterall!).

I also don't care for "soft-versioning" or "optimistic versioning" (dependencies that have ^, x, > in them, or anything other than numbers and dots). There have been too many problems with bad semantic versioning in dependencies, and I'd rather have a solid library than a bleeding edge one.