#239)

Bumps [http-proxy](https://github.com/http-party/node-http-proxy) from 1.17.0 to 1.18.1.
- [Release notes](https://github.com/http-party/node-http-proxy/releases)
- [Changelog](https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md)
- [Commits](http-party/node-http-proxy@1.17.0...1.18.1)

Signed-off-by: dependabot[bot] <[email protected]>

…-1.18.1

Bump http-proxy from 1.17.0 to 1.18.1

This was occasionally causing my machine to spin on CPU indefinitely
while trying to download the Closure Compiler output.

It would perhaps be better to investigate what is wrong with curl on my
machine, but since Node has a pretty nice built-in HTTPS client, I
figured it'd be easier to just cut out the external system dependency
entirely.

fs.writeFileSync no longer stringifies arguments, instead throwing if it
receives something that is not a proper String or Buffer.

This is the last item preventing node-tap from being browser-friendly.
Since global.process is safely guarded in other instances where it is
used, this seems like an oversight.

…bal-process

Isaacs/do not break on missing global process

`register-hook-require` entry point