Walked through all the dependencies with npm outdated and manually updated and tested the respective functionality changed.
Also updated the node engine requirements. I'll try against the Node lifecycle, but will likely be fairly slow. Especially as Node become more ES6+ stable there likely won't be many problems with any dev dependencies for older versions. I will continue to target ES5 for the actual library, though.
Coverage remained the same at 100.0% when pulling a7344be0f744fccb22e9d24ce5df6da03cecea10 on master_/package-vulnerabilities into 6a0da84aa47017bb6d5fe854b5e6abe0c536953f on master.
Completes #28
Walked through all the dependencies with
npm outdated
and manually updated and tested the respective functionality changed.Also updated the
node
engine requirements. I'll try against the Node lifecycle, but will likely be fairly slow. Especially as Node become more ES6+ stable there likely won't be many problems with any dev dependencies for older versions. I will continue to target ES5 for the actual library, though.