Pretty self explanatory, but this project needs to hook up to some CI service in order to run automated tests (see #8) and potentially also publish new versions automagically on version bumps. (That latter bit being scary and possibly dangerous, so may want to reconsider.)
By far the two popular choices for OSS these days, and in particular JS projects, are Travis CI and Wercker. Of those, the latter has the interesting bonus feature of allowing you to define environments using Docker containers, which can even be used to provide a consistent local development environments (see #7.)
mstade
commented
9 years ago
Pretty self explanatory, but this project needs to hook up to some CI service in order to run automated tests (see #8) and potentially also publish new versions automagically on version bumps. (That latter bit being scary and possibly dangerous, so may want to reconsider.)
By far the two popular choices for OSS these days, and in particular JS projects, are Travis CI and Wercker. Of those, the latter has the interesting bonus feature of allowing you to define environments using Docker containers, which can even be used to provide a consistent local development environments (see #7.)