a64859b4bc
When compiling the flat-file version of the `@angular/core` we need to be aware that we cannot rely upon imported names to access the ivy definition functions. The compiler is already clever enough to use local function calls rather than trying to add a namespaced import, but there is a problem if the local name of the function is different to the exported name. This is the case for functions that are not part of the public API, and so are exported under a barred-O private alias. In `@angular/core` the only decorations in use are `@NgModule` and `@Injectable`. There are no directives, components, pipes, etc. Since `defineInjectable` is part of the public API of `@angular/core`, the compiler is able to generate code that references the original non-barred-O version of the function. But the `defineNgModule` is not part of the public API and so the compiler must generate code that refers to it by the private barred-O version of the function. This commit imports and then re-exports this barred-O version of `defineModule` to ensure that the symbol is available in the local scope of the flat-file versions of the `@angular/core` library. PR Close #26403 |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| testing | ||
| BUILD.bazel | ||
| PACKAGE.md | ||
| index.ts | ||
| package.json | ||
| public_api.ts | ||
| rollup.config.js | ||
| tsconfig-build.json | ||