@ryanjyoder, Thank you reporting this issue!
I am encountering by the very same issue when trying to include node and postcss-cli in the Hugo snap:
node:
plugin: nodejs
node-packages: [postcss-cli]
filesets:
node:
- bin/node
postcss:
- bin/postcss
- lib/node_modules/postcss-cli/*
prime:
- $node
- $postcss
where npm fails to fetch postcss-cli failing with the same network proxy issue:
npm --cache-min=Infinity install --global postcss-cli
[24/Aug/2018:15:51:26 +0000] "CONNECT nodejs.org:443 HTTP/1.0" 200 14030940 "-" "-"
[24/Aug/2018:15:51:32 +0000] "CONNECT registry.npmjs.org:443 HTTP/1.1" 503 1956 "install postcss-cli" "npm/3.10.10 node/v6.11.4 linux x64"
[24/Aug/2018:15:51:42 +0000] "CONNECT registry.npmjs.org:443 HTTP/1.1" 503 1956 "install postcss-cli" "npm/3.10.10 node/v6.11.4 linux x64"
[24/Aug/2018:15:52:42 +0000] "CONNECT registry.npmjs.org:443 HTTP/1.1" 503 1956 "install postcss-cli" "npm/3.10.10 node/v6.11.4 linux x64"
npm ERR! Linux 4.4.0-128-generic
npm ERR! argv "/build/hugo/parts/node/install/bin/node" "/build/hugo/parts/node/install/bin/npm" "--cache-min=Infinity" "install" "--global" "postcss-cli"
npm ERR! node v6.11.4
npm ERR! npm v3.10.10
npm ERR! code ECONNRESET
npm ERR! network tunneling socket could not be established, statusCode=503
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /build/hugo/parts/node/src/npm-debug.log
Failed to run 'npm --cache-min=Infinity install --global postcss-cli' for 'node': Exited with code 1.
See the full build log at
https://launchpadlibrarian.net/385171998/buildlog_snap_ubuntu_xenial_amd64_hugo_BUILDING.txt.gz
Thanks in advance to the Snapcraft.io gurus for help!