Broken: node-gyp http requests not proxied

[andrew]

Currently you can't succesfully npm install node-sass when using forest as a proxy as one of the post-install scripts attempts to download extra binaries from github releases (https) whilst reusing the same proxy as npm, which breaks as we don't have ssl configured with forest yet.

Closely related to #27, we need proper ssl support and certs configured for node-http-proxy.

This isn't a problem for go support, only certain npm modules.

[andrew]

https://github.com/davewasmer/devcert may be a nice solution to this

[andrew]

Switched the approach with npm to using npm config set registry=http://0.0.0.0:8005/ instead of proxying which sidesteps the ssl issues.