{"id":924,"date":"2012-12-31T16:11:57","date_gmt":"2012-12-31T15:11:57","guid":{"rendered":"https:\/\/www.unicoda.com\/?p=924"},"modified":"2012-12-31T16:11:57","modified_gmt":"2012-12-31T15:11:57","slug":"npm-noproxy-configuration","status":"publish","type":"post","link":"https:\/\/www.unicoda.com\/?p=924","title":{"rendered":"NPM: noproxy Configuration"},"content":{"rendered":"

\"\"<\/p>\n

For security reasons, every firms are generally using a proxy to manage their internet connection. Coding behind a proxy is fine. Most softwares are able to deal with it. You just have to set it in the environment variable of your GNU\/Linux OS or directly in the software.<\/p>\n

But there is one problem. Because every request must go through the proxy, it’s impossible to request url based in the internal network. There is only one solution: disable proxy, make request, enable proxy. If you are using npm until now, that’s what you have to do.<\/p>\n

In order to make this process easier, I’ve made a pull request which add a noproxy configuration. When npm<\/a> fetches a package from a given url, the hostname is compared with noproxy configuration. If there is a match, the request is made without proxy, if not proxy is used.<\/p>\n

The noproxy configuration looks for a variable named \u00ab\u00a0noproxy\u00a0\u00bb in npm configuration.
\n\u00ab\u00a0noproxy\u00a0\u00bb is a string containing hostnames. So, this list of hostnames will not ever go through a proxy.
\nCode concerned:<\/p>\n

var proxy = null\r\nif(npm.config.get(\"noproxy\").search(remote.hostname) === -1) {\r\n\u00a0 if (remote.protocol !== \"https:\" || \r\n      !(proxy = npm.config.get(\"https-proxy\"))) {\r\n\u00a0\u00a0\u00a0 proxy = npm.config.get(\"proxy\")\r\n\u00a0 }\r\n}\r\n\r\nvar opts = { url: remote\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 , proxy: proxy\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 , strictSSL: npm.config.get(\"strict-ssl\")\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 , ca: remote.host === regHost ? \r\n                                npm.config.get(\"ca\") : undefined\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 , headers: { \"user-agent\": npm.config.get(\"user-agent\") }}\r\n\r\nvar req = request(opts)<\/pre>\n
At the moment, I’m still waiting for Isaacs to add the pull request in npm<\/a>.
\nI hope it will be added soon.<\/p>\n
Update:<\/strong> \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Isaacs has pointed out that it’s good for the npm bit but some modifications are still needed in\u00a0npm-registry-client<\/a>\u00a0and\u00a0npmconf<\/a>\u00a0. So here are new additions:<\/p>\n