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

packagerChrome.py

Index: packagerChrome.py
diff --git a/packagerChrome.py b/packagerChrome.py
index 4b199953b8ea6ba0e56759d42eee395d03091e0d..1fdc679411413f39a43787678eb3d7548abec98e 100644
--- a/packagerChrome.py
+++ b/packagerChrome.py
@@ -2,6 +2,7 @@
 # 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/.
 
+import ConfigParser
 import errno
 import glob
 import io
@@ -155,6 +156,21 @@ def create_bundles(params, files, bundle_tests):
         'edge': 'edgeInfo.js.tmpl',
         'gecko': 'geckoInfo.js.tmpl',
     }
+    aliases = {
+        # To use our custom loader for the info module we must first set up an
+        # alias to a file that exists.
+        'info$': os.path.join(os.path.dirname(__file__), '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',
+    }
+    try:
+        aliases.update(params['metadata'].items('module_alias'))

[kzar, 2018/04/30 14:00:14]

I guess maybe we should make the vales an absolute path relative to the metadata
file that the entry came from?

+    except ConfigParser.NoSectionError:
+        pass
 
     # Historically we didn't use relative paths when requiring modules, so in
     # order for webpack to know where to find them we need to pass in a list of
@@ -174,6 +190,7 @@ def create_bundles(params, files, bundle_tests):
         'extension_path': base_extension_path,
         'info_module': info_module,
         'resolve_paths': resolve_paths,
+        'aliases': aliases,
     }
 
     for item in params['metadata'].items('bundles'):