Commit b9c78d7 introduces ES6 code that makes it impossible to use this module with node.js v0.10 and v0.12. It also removes CI coverage for those versions so it looks like the change was intentional.
That would be perfectly acceptable if it had been published as v2.0.0 but because it's a minor release, it breaks the build for people that diligently put "optional-dev-dependency": "^1.0.0" in their package.json.
No action required - reverting and publishing v1.4.1 or v1.5.0 would be a semver violation too, if I read the changelog right - but perhaps it's something you can keep in mind next time.
Commit b9c78d7 introduces ES6 code that makes it impossible to use this module with node.js v0.10 and v0.12. It also removes CI coverage for those versions so it looks like the change was intentional.
That would be perfectly acceptable if it had been published as v2.0.0 but because it's a minor release, it breaks the build for people that diligently put
"optional-dev-dependency": "^1.0.0"in their package.json.No action required - reverting and publishing v1.4.1 or v1.5.0 would be a semver violation too, if I read the changelog right - but perhaps it's something you can keep in mind next time.