CI / CD

It would be nice if the project has some continuous integration support. I think we could probably put something together pretty easily with travis. I am happy to send a PR!

Even more interesting would be continuous deployment. Perhaps based on tags landing in the repo? It would depend on this project's release method/strategy. Perhaps we can talk about releasing, and I can document that process, as a first step? After that we can look at automating.

No files or tests are named. Start by reviewing the repository's existing release method and npm/yarn publishing configuration, then discuss the CI scope and release strategy with maintainers. Done means the release process is documented and the scope of any tag-based deployment is agreed.

Written by the indexing model from the issue text.