npm Proxy Failures During Install-Script Downloads
An npm package can run a separate download during installation. Identify that program and host instead of assuming every request uses npm's registry proxy configuration.
If an npm installation gets past the registry download and stops in an install script, identify the second downloader. The JavaScript package may already be present while its platform-specific binary is still missing.
- Find the request owner in the log. Record the lifecycle script, executable or HTTP library, destination hostname and first error. A package can launch another program whose download is separate from npm's registry transfer.
- Use that downloader's supported proxy interface. For tfjs-node's resources.js path, the child process's proxy environment is one concrete example. Check the package's documented download settings and the environment of the process making the request. A standard proxy variable helps only if that consumer reads it; adding similarly named variables does not establish support.
- Follow the actual artifact route. Release servers, object stores and redirect targets can differ from the registry. Compare proxy authentication, approved destinations and TLS trust for the request that failed.
Do this before clearing caches: the log's transition from package retrieval to lifecycle execution already narrows the fault. Successful registry access is useful comparison evidence, but it does not establish that the secondary program supports the same route or can reach its artifact host.
Disabling install scripts can skip the download and leave the package unusable. If the package documents an approved prebuilt or offline installation path, prepare that artifact deliberately and confirm the executable is available before treating installation as complete.