872a3656fe
Currently external static symbols which are referenced by AOT compiler generated code, will be re-exported in the corresponding `.ngfactory` files. This way of handling the symbol resolution has been introduced in favor of avoding dynamically generated module dependencies. This behavior therefore avoids any strict dependency failures. Read more about a particular scenario here: https://github.com/angular/angular/issues/25644#issuecomment-458354439 Now with `ngtsc`, this behavior has changed since `ngtsc` just introduces these module dependencies in order to properly reference the external symbol from its original location (also eliminating the need for factories). Similarly we should provide a way to use the same behavior with `ngc` because the downside of using the re-exported symbol resolution is that user-code transformations (e.g. the `ngInjectableDef` metadata which is added to the user source code), can resolve external symbols to previous factory symbol re-exports. This is a critical issue because it means that the actual JIT code references factory files in order to access external symbols. This means that the generated output cannot shipped to NPM without shipping the referenced factory files. A specific example has been reported here: https://github.com/angular/angular/issues/25644#issue-353554070 PR Close #28594 |
||
|---|---|---|
| .. | ||
| compiler.ts | ||
| compiler_factory.ts | ||
| compiler_host.ts | ||
| compiler_options.ts | ||
| formatted_error.ts | ||
| generated_file.ts | ||
| lazy_routes.ts | ||
| partial_module.ts | ||
| static_reflector.ts | ||
| static_symbol.ts | ||
| static_symbol_resolver.ts | ||
| summary_resolver.ts | ||
| summary_serializer.ts | ||
| util.ts | ||