reference-core

Angular dependency injection functions through two primary systems: Module Injectors and Node Injectors. This dual-injector architecture handles service instantiation and hierarchical provider resolution across the framework's component tree.

Angular's rendering engine uses an instruction-based approach within the Ivy architecture. This design translates template logic into imperative instructions, managing DOM updates and view generation directly.

To understand Angular's core architecture, review the SKILL.md file which details the internal design principles. It explains the mental model, key directories, and conventions used within the framework's core code.

Yes, the reference covers both Module Injectors and Node Injectors within the dependency injection system. It explains how these two injector hierarchies resolve dependencies and manage service instantiation across the framework.

Angular's Ivy rendering engine uses an instruction-based architecture to optimize view generation and DOM updates. This design replaces older template approaches, streamlining compilation and reducing runtime overhead.

Angular's change detection relies on dirty checking, which can introduce performance overhead in large component trees. The framework addresses this limitation by introducing new reactivity primitives to optimize view updates.