Updated node-gyp to 8.1.0

[darkmatter18]

What / Why

• Updating the node-gyp version to 8.1.0
• Many packages depend on run-script, so being a major package, it's so bad to use a deprecated package
• That's why I updated the node-gyp to 8.1.0

References

Related to #25
Fixes #25
Closes #25

[wraithgar]

Because our support contract in npm includes >=10, we can not update node-gyp to v 8 until we drop v10 support.

node-gyp@8 requires >= 10.12.0 of nodejs because it uses the recursive flag for mkdir:

https://github.com/nodejs/node-gyp/blob/5f1a06c50f3b0c3d292f64948f85a004cfcc5c87/lib/configure.js#L75

[silkfire]

@wraithgar When will npm drop v10 support?

[bedwardly-down]

@wraithgar Currently doing some research on this issue and testing some small things out (seeing request as a dependency bugs me for my own uses). I'm looking into figuring a replacement that could work instead.

Findings:

• Axios 0.21.4 (current version) tests without issues on Node 10.0.0 even though it doesn't explicitly state what versions it supports
• Latest release of tap has several failures on Node 10.0.0 but the version used here seems to not like Axios
• Postman and Cypress, two of the more popular modern request forks that seem to be getting fairly regular maintenance, rely on dependencies such as karma-tap which npm suggests to avoid installing

[wraithgar]

Next month we are planning on cutting npm@8 which drops node 10 support. node-gyp@8 will be a part of that release and we will stay current w/ node-gyp as long as it doesn't drop support for any node12 before it went LTS