Comment 4 for bug 1611372

Thanks for bringing this up and for your code!

From what I understood after reading the npm issue and the PR, I don't think this should be worked around in snapcraft.

If your https proxy is not good to work with npm, the solution is not going to be to always use the http proxy instead. I think snapcraft should just respect the environment, so you would fix this by setting npm_config_https_proxy to whatever is correct for your network, before calling snapcraft.