The previous implementation was calling moduleMerge multiple times for a
required module if it had more than one configured global lazy-loaded
functions/properties. We now keep tracked of merged modules and merge only
the first time.
Exposes a module registration API, that webpack users can use to bundle
"dynamic" modules that are required through some variable.
Falls back to the require API if no module is registered.
Reworked dynamic `require` code to use module-loader:
- navigation: ui/frame.
- XML UI build ui/builder/builder and ui/builder/component-builder.
- module on-demand loads in global functions: globals.
- Use relative imports in place of most of our absolute ones.
- Add "private" ambient modules for modules that we need to import using
an absolute path (e.g. when app/.../test-something.ts needs to import
ui/styling/style-scope)
Removing __extends function generation by setting the
noEmitHelpers flag we removed the __decorate as well.
While the __extends exists in the runtimes, __decorate
is an EcmaScript-related functionality, hence its place
is in the modules.
