npm Works, but tfjs-node's Native Resource Download Misses the Proxy
Set the environment read by scripts/resources.js, and check its first-nonempty variable order before changing npm configuration again.
For tfjs-node's scripts/resources.js download path, give the child process its proxy environment. In the PowerShell session launching the package operation:
$env:HTTPS_PROXY = 'http://proxy.example:8080'
$env:HTTP_PROXY = 'http://proxy.example:8080'Start the intended operation from that session. For a permitted public resource download, use an HTTP endpoint from the HTTP proxy list in these values. The script reads process.env in this order, taking the first nonempty value: HTTPS_PROXY, https_proxy, HTTP_PROXY, http_proxy. A stale earlier value can hide the change you made later in the list.
A working npm registry request tests another downloader. Its .npmrc proxy entry need not supply a process variable used by the native-resource script. Keep the failed URL with the download stage to identify which input is missing.
This order belongs to the stated resource implementation. Match it to the installed tfjs-node release's downloader instead of patching a cached script with another version's assumptions.