add travis for continuous integration testing #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
I found we were unable to compile our templates using node 12, so I wanted to add travis to this project to be able to test updating to a new version of eco.
I also found that this fixes #14
How this was tested
I enabled travis on my fork cesine#2, and used it to find which versions of node still worked. I found a pretty positive result, this repo can still run with node versions 6 and above. It will be able to work with node 0.12 in the future if the ejs patch is accepted so i kept 0.12 in the list of versions in the travis.yml.
Node <= 0.12 https://travis-ci.com/github/cesine/grunt-eco/jobs/363481531 fails due to mde/ejs#534
Node <= 6 https://travis-ci.com/github/cesine/grunt-eco/jobs/363475715 fails due to mkdirp
The root cause is mkdir is using es6 after v 1.0.0 isaacs/node-mkdirp@ed0ae94#diff-3ca2c4508c333566c2fe17e2a75c5863
and grunt dropped support for older versions of node in gruntjs/grunt@4bfa98e#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 v 1.1.0
Node > 8 https://travis-ci.com/github/cesine/grunt-eco/jobs/363475717#L216