Update node-pre-gyp to fix security issues

[crutchcorn]

Because node-pre-gyp v0.9.1 has a dependency that opens security issues, I updated the version to 0.10.0 in order to fix this. I've ran tests and they all passed perfectly fine. That being said, I had to bump the version of Node supported to 6 rather than 4 (as pre-gyp drops support for 4 due to EOL upcoming) and thusly updated the major version of the package to 3.0.0 rather than 2.0.2 or 2.1.0 because of how semver works.

Either way, not a massive change.

Fixes #604

[fluxsauce]

@crutchcorn broken on Node 6?

[crutchcorn]

Well that's not ideal @fluxsauce . It seems that it's running Object.entities which was introduced in NodeJS 7 - not 6. I'll look into it because node-pre-gyp was not documented dropping Node 6, so that should be fixed.

[lahdekorpi]

Any updates on this?
npm install on the latest version shows that a vulnerability is found.
And npm audit is currently showing a warning about this...

The PR shows that the major of this package is going to update to 3, so why not merge this with a Node 7 requirement. And then figure out a solution for the older major?

[simonmeusel]

@crutchcorn Why are the node 4 and node 5 builds working then? And why is only the MacOS build failing?

If it's only because of Object.entities, then the build with prior versions of node should also be failing.

https://travis-ci.org/kelektiv/node.bcrypt.js/builds/376661218

[recrsn]

@lahdekorpi It will not be possible to just drop a supported LTS release.

Although the issue is rated as moderate, it is rated as low for us, as we do not use the module in run-time. Even the module is not invoked while installing from npm.

[recrsn]

Please do not make this increment. We will release with a CHANGELOG and the increment is done as the part of it.

[paulbjensen]

The tests on Travis are all passing, so if the review item to revert the version change gets done, will this item be good to merge?

not required

[recrsn]

I'll cut a release on Sunday

[hfsd]

@agathver Please publish on npm.

[thom-nic]

@agathver sorry for the ping, any update on when this will publish on npm?