Otherwise installing with npat turned on fails, because it can't find the test runner.
What is npat?
It's cpants for npm :)
You can join the party now, if you want: npm config set npat true, and then installs will fail if tests fail. In a future release, it'll also upload test success/failure data to a server, so package authors can see where their stuff works and where it doesn't.
npm config set npat true
These tests will fail anyway. Because the user needs to configure their own loggly account before running them. It's in the docs.
I feel like this npat thing (while nice) is pretty edge case. Maybe it should just look in both places?
If you install with --npat set, then it'll install devDependencies as well, since that's where test stuff usually goes.
The loggly tests exit successfully with a message on my machine if I install vows first. So, they "pass", albeit trivially.
[dist] Update package.json, and .gitignore. Update require statements…
… to be more future proof. Fixes #8