This bug tracks investigation work on the format in which the open-sourced MR extension should be bundled with Chromium. Some points to consider:
- Whether it is possible to load the open-source MR extension as an internal component extension in Chromium. This should be overridable if we loaded a custom MR extension build.
- Barring that, we can create a GN build target that generates a set of extension files in the output directory, that can be loaded manually.
- At the minimum, there should be Closure compiler type checking of the code (that is also enabled on the waterfall), and creating bundled JS files from sources that continues to work with mr.Module.
-- dbeam@ is a good POC to consult with regarding the use of Closure compiler.
- goog.module / goog.provide / goog.require will need to be compiled out, or removed manually, or we need to provide a stub definition.