reference-compiler-cli

The Angular compiler-cli architecture handles decorator processing through DecoratorHandlers within the TraitCompiler, analyzing components, directives, pipes, and NgModules across lazy analysis and trait lifecycle phases to manage metadata and emit transformations.

Template type checking in ngtsc operates through a pipeline that generates type check blocks to validate Angular templates. This mechanism is integrated into the NgCompiler to ensure template expressions are statically verified against TypeScript types during the compilation process.

To analyze code in packages/compiler-cli, you must understand its lazy, incremental, and partial compilation pipeline. This involves tracing how NgtscProgram coordinates analysis, resolution, and emit phases through the TraitCompiler and NgCompiler subsystems.

Yes, the Angular compiler-cli supports incremental and partial compilation through its coordinated pipeline. It utilizes lazy analysis and the trait lifecycle to efficiently process changes without recompiling the entire program, enabling faster builds via NgtscProgram.

The best way to understand scope resolution in ngtsc is examining the MetadataReader and ScopeRegistry. These subsystems wire dependencies across NgModules, ensuring that directives and pipes are correctly mapped and available during template type checking.

Ngtsc wraps the TypeScript compiler to intercept and transform code during the emit phase. This architecture allows it to generate Ivy instructions and remove legacy decorators while preserving TypeScript's native type checking and emit capabilities.