<!--
Thanks for helping out!  To make sure your pull request goes smoothly, here's a quick checklist to walk through:

✔ Write a summary

Please summarize your change, and provide as much context as you can.  What's your motivation for the change?  Why'd you take this approach?  Links to related issues?  Etc.  Helps the reviewer give more thoughtful feedback.

✔ Tests!

This repository requires a decent amount of coverage on all changes, in an effort to keep master green.  So, please write tests for any new feature you write - and, if possible, regression tests for bugs you've fixed.

✔ Bump the version if needed

This repository automatically publishes every commit on master to npm, and increments the Z version for you.  So:

* Fixing a bug?  Thanks!
  You don't need to touch the version.

* Adding a new, backwards-compatible, feature?  Sweet!
  Please increment the Y version in package.json.

* Making a breaking change to an existing API?  Welp, that's how it goes.
  Please increment the X version in package.json.

-->