355e54a410
Libraries can expose directive/component base classes that will be used by consumer applications. Using such a base class from another compilation unit works fine with "ngtsc", but when using "ngc", the compiler will thrown an error saying that the base class is not part of a NgModule. e.g. ``` Cannot determine the module for class X in Y! Add X to the NgModule to fix it. ``` This seems to be because the logic for distinguishing directives from abstract directives is scoped to the current compilation unit within ngc. This causes abstract directives from other compilation units to be considered as actual directives (causing the exception). PR Close #33347 |
||
|---|---|---|
| .. | ||
| 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 | ||