Issue 5060 - Move require into modules template, make info a module

templates/modules.js.tmpl

Index: templates/modules.js.tmpl
diff --git a/templates/modules.js.tmpl b/templates/modules.js.tmpl
index c826d892704589d344ecb9fadb61348ab8448b3b..39f3bd302e8e0f10d4badd3d5e61e94dd0a4dd68 100644
--- a/templates/modules.js.tmpl
+++ b/templates/modules.js.tmpl
@@ -1,4 +1,31 @@
 {%- if args["module"] -%}
+if (typeof require != "function")

[kzar, 2017/04/01 01:32:57]

As discussed in IRC this is safer, since if a webpage has an element of id
"require" then `require` evaluates to it and so `typeof require == "object"`, at
least by the time the postload scripts run.

[Sebastian Noack, 2017/04/01 10:02:56]

Wow, I never noticed that named elements become automatically available in the
global namespace. This is crazy. After reading up on it, I figured that IE first
introduced this mess (of course), then other browsers had to follow for
compatibility (since back in the days every website targeted IE), and eventually
it even made it into the standard:
https://www.w3.org/TR/html5/browsers.html#named-access-on-the-window-object

+{
+  var require = function(module)
+  {
+    if (!(module in require.scopes))
+    {
+      let scope = {exports: {}};
+      require.scopes[module] = require.modules[module](scope, scope.exports);
+    }
+    return require.scopes[module];
+  };
+  require.modules = Object.create(null);
+  require.scopes = Object.create(null);
+}
+
+{% if args["injectinfomodule"] %}
+require.modules["info"] = function(module, exports)
+{
+{% if type == "gecko-webext" %}
+{% include "geckoInfo.js.tmpl" %}
+{% elif type == "chrome" or type == "edge" %}
+{% include "chromeInfo.js.tmpl" %}
+{% endif %}
+return module.exports;
+};
+{% endif %}
+
 {%- for module_name, script in modules -%}
 require.modules[{{ module_name|json }}] = function(module, exports)
 {