Incorrect noproxy argument in documentation

(Illan RUL-DA CUNHA) #1

What I Wanted to Do

I am using npm behind a corporate proxy, and I wanted to exclude our internal package manager (its URL) from the proxy. I put a noproxy=“address_to_exclude” in my .npmrc, as noted in the documentation (

What Happened Instead

The build was taking noproxy as a correct variable, but it didn’t exclude the address of the package manager and it failed when trying to access it to get packages.


Is it possible to correct the documentation to say that the correct variable is no_proxy (with an underscore) and not noproxy?

Thank you very much, have a great week. ;)

(Nikki Everett) #2

Hi Illan – noproxy is the correct variable for the latest version of npm (6.4.1); if you’re using an older version of npm, you can update with npm install npm@latest -g and use the noproxy config variable.

If you don’t want to update npm, you can do one of the following:

  • change the config variable to no-proxy; or
  • set the NO_PROXY environment variable

Let me know if you run into any more trouble or have any other questions.

(system) closed #3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.