Closed keithmorris closed 4 years ago
@niftylettuce Would love your thoughts on this PR.
I don't think we should drop support for Node 6 to be honest. There is not a valid reason why we should suddenly drop the support.
Like other packages out there, we should be as far back compatible as possible.
I wanted to update all package dependencies as there were potential security issues in some of the required packages. Some of these updated dependencies no longer support Node < 8 and as such, the library has been set to have the node engine requirement at Node >= 8. Travis test script has removed Node 6 and added Node 12.
This seems acceptable to me as Node < 8 is no longer supported and Node 8 will only be supported through 2019-12.31.
Although there is no change in functionality, I have bumped the version to 3.0.0 in case anyone is using the 2.x.x version in Node 6/7 it will not cause the library to fail as long as their
package.json
file indicates the"^2.7.0"
syntax to lock their version at the 2.x.x release.