install: Support for --no-proxy configuration (npm#19157)

This commit adds support for the noProxy configuration.

All whats really needed is passing the option to the `pacote` package,
this will pass it to `make-fetch-happen` and finally to the `request`
package where this is implemented.

Fixes: npm#18350
Fixes: npm#7168
PR-URL: npm#19157
Credit: @Saturate
Reviewed-By: @zkat

doc/misc/npm-config.md

@@ -675,6 +675,13 @@ impact how lifecycle scripts are called.
 
 The node version to use when checking a package's `engines` map.
 
+### no-proxy
+
+* Default: null
+* Type: String or Array
+
+A comma-separated string or an array of domain extensions that a proxy should not be used for.
+
 ### offline
 
 * Default: false

lib/config/defaults.js

@@ -193,6 +193,7 @@ Object.defineProperty(exports, 'defaults', {get: function () {
     'progress': !process.env.TRAVIS && !process.env.CI,
     proxy: null,
     'https-proxy': null,
+    'no-proxy': null,
     'user-agent': 'npm/{npm-version} ' +
                     'node/{node-version} ' +
                     '{platform} ' +
@@ -312,6 +313,7 @@ exports.types = {
   'metrics-registry': [null, String],
   'node-options': [null, String],
   'node-version': [null, semver],
+  'no-proxy': [null, String, Array],
   offline: Boolean,
   'onload-script': [null, String],
   only: [null, 'dev', 'development', 'prod', 'production'],

lib/config/pacote.js

@@ -37,6 +37,7 @@ function pacoteOpts (moreOpts) {
     preferOnline: npm.config.get('prefer-online') || npm.config.get('cache-max') <= 0,
     projectScope: npm.projectScope,
     proxy: npm.config.get('https-proxy') || npm.config.get('proxy'),
+    noProxy: npm.config.get('no-proxy'),
     refer: npm.registry.refer,
     registry: npm.config.get('registry'),
     retry: {