Issue 6625 - Expose webpack's resolve.alias to the packagers

webpack_runner.js

 /* This Source Code Form is subject to the terms of the Mozilla Public
  * License, v. 2.0. If a copy of the MPL was not distributed with this
  * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
 
 "use strict";
 
 const path = require("path");
 const process = require("process");
 
 const MemoryFS = require("memory-fs");
 const webpack = require("webpack");
 
 // We read the configuration from STDIN rather than as an argument to improve
 // the output on error. Otherwise the (fairly huge) configuration is printed
 // along with the actual error message.
 let inputChunks = [];
 process.stdin.setEncoding("utf-8");
 process.stdin.on("data", chunk => { inputChunks.push(chunk); });
 process.stdin.on("end", () =>
 {
   let {bundles, extension_path,
-       info_module, resolve_paths} = JSON.parse(inputChunks.join(""));
+       info_module, resolve_paths, aliases} = JSON.parse(inputChunks.join(""));
 
   // The contents of the info module is passed to us as a string from the Python
   // packager and we pass it through to our custom loader now so it is available
   // at bundle time.
   require("./info-loader").setInfoModule(info_module);
 
   // Since the cost of starting Node.js and loading all the modules is hugely
   // larger than actually producing bundles we avoid paying it multiple times,
   // instead producing all the bundles in one go.
   let options = [];
@@ skipping 11 matching lines @@
       entry: entry_points,
       output: {
         path: path.resolve(""),
         filename: bundle_name
       },
       node: {
         global: false
       },
       resolve: {
         modules: resolve_paths,
-        alias: {
-          // To use our custom loader for the info module we must first set up
-          // an alias to a file that exists.
-          info$: path.join(__dirname, "info.js"),
-          // Prevent builtin Node.js modules from being used instead of our own
-          // when the names clash. Once relative paths are used this won't be
-          // necessary.
-          url$: "url.js",
-          events$: "events.js",
-          punycode$: "punycode.js"
-        },
+        alias: aliases,
         plugins: [
           function()
           {
             // Our old module system in packagerChrome.py used to prefix
             // module names with the name of their parent directory and an
             // underscore - but only when that directory wasn't called
             // "lib". This plugin is for backwards compatability, but can
             // be removed once use of that deprecated syntax has been
             // replaced.
             this.plugin("described-resolve", (request, callback) =>
@@ skipping 74 matching lines @@
               included.add(path.relative(extension_path, module.name));
           }
         }
       }
       output.included = Array.from(included);
 
       console.log(JSON.stringify(output));
     }
   });
 });