continuous integration

[oprogramador]

Could you add a CI so we could easily see whether the tests are passing and whether the code from this repo (but not any other code which maybe is missing in this repo) is published to NPM?

[gmsorrow]

@oprogramador CI tests are setup.
Please feel free to add NPM publish to Circle CI config.

[oprogramador]

@gmsorrow

Can I also add semantic-release which not only publishes to NPM but also bumps NPM versions (with pushing to GitHub)?

[gmsorrow]

@gmsorrow

Can I also add semantic-release which not only publishes to NPM but also bumps NPM versions (with pushing to GitHub)?

Sure.

[oprogramador]

@gmsorrow

I opened #13

Before merging, you'll need to set the following env variables in CircleCI:
GITHUB_TOKEN
NPM_EMAIL
NPM_TOKEN

I haven't tested this PR but a similar code works for my repos though they use Travis CI.

If the build fails due to generating an already published version, I recommend running git commit -m 'feat: an empty commit to test semantic release' --allow-empty --no-verify && git push origin master until the build passes because semantic release doesn't seem to recognize versions created manually.