I had the same problem: we have a private Nexus npm repository where we host some custom modules, and we need npm not to use a proxy when requesting these packages.
The only reliable solution I found for Windows was to specify the environment variables that you specified and actually delete all proxy values from npm (set proxy , https-proxy and https_proxy all to null in the .npmrc file).
So, for example, the .npmrc file in the root of the project looks like this:
strict-ssl=false ca=null registry=http://my-nexus-repo.com/repository/npm-packages/ my-custom-registry-on-nexus:registry=http://my-nexus-repo.com/repository/hosted-npm-packages/ https_proxy=null https-proxy=null proxy=null
no_proxy above example, the environment variable no_proxy will look something like this:
my-nexus-repo.com,localhost
This allowed us to easily install all npm packages (even complex ones like node-sass that load tarballs outside of npm).
source share