ebc8e808a9
When lazily loading code, users need to be able to get hold of the NgModuleFactory. For SystemJS environments, the SystemJS registry serves this purpose. However other environments, such as modules compiled with Closure compiler, do not expose exports object or a path based registry. For these environments, `@NgModule` objects can include an identifier, and the loading code can then pass `loadModule(id).then(() => getNgModule(id))` to the router. |
||
|---|---|---|
| .. | ||
| @angular | ||
| angular1_router | ||
| benchmarks | ||
| benchmarks_external | ||
| e2e_util | ||
| payload_tests/hello_world/ts | ||
| playground | ||
| rollup-test | ||
| empty.ts | ||
| es6-subset.d.ts | ||
| system.d.ts | ||
| tsconfig.json | ||
| types.d.ts | ||