[V2] (Suggestion) Continuous Integration

[InzeNL]

Currently, V2 of tmi.js is being worked on. If the decision is ever made to implement continuous integration, it would be smarter to do this now, while it is still being built up, than later on, when it is "done". This prevents having to rewrite code later on to have it meet set standards.

Continuous integration demands higher code quality, if set up correctly, and reduces the risk of code breaking unexpectedly.

Before implementing this I would like to gauge what people think of this. I would also like to get a list of suggestions for CI tools.

I myself would suggest to have at least these:

• Build success
  • TravisCI is free for open-source projects
• Test Coverage (% TBD)
  • mocha + nyc are already implemented
• Mutation Coverage (% TBD)
  • @stryker-mutator/core is widely used to mutate JS
• Linters (Note: V2 is being written in TS, transpiled to JS)
  • TSLint

[StevenKowalzik]

As TSLint will be deprecated this year, eslint-typescript should be used as a replacement for linting.