make protoc installation script respect proxy env

[mikonse]

see #507

[timostamm]

The package looks decent. But should this be a peer dependency?
I'd expect a peer dependency for a host library (see the npm docs).

Happy to learn if there is a good reason, otherwise, best to go with a direct dependency here.

[mikonse]

You're right, I was thinking of this package being installed in a broader host context but since this is a hard requirement of this installation script making it a peer dependency does not make much sense.

[timostamm]

Hm I had to revert this in 3a5b9f9, unfortunately.

CI failed with:

lerna ERR! npm ci exited 1 in '@protobuf-ts/protoc'
lerna ERR! npm ci stderr:
npm ERR! Cannot read property 'proxy-agent' of undefined

And a local install failed with:

lerna info Bootstrapping 22 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 1 in '@protobuf-ts/protoc'
lerna ERR! npm install stderr:
npm ERR! code ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to https://npm.rsint.net/api/npm/rs_npm_virtual/xregexp/-/xregexp-2.0.0.tgz failed, reason: getaddrinfo ENOTFOUND npm.rsint.net

[mikonse]

It seems I've made a small error with where I've regenerated the package-lock.json as I've had a local npm mirror configured.

If you just delete the package-lock.json and rerun npm install ist should generate a valid package-lock.json