The theory of Angular Ivy
summary
Angular Ivy replaces View Engine with a new compiler/runtime that compiles decorators into static ngDef fields and emits an imperative instruction set so templates and change detection are tree-shakable. Claims: hello‑world bundles drop to about 4.5 KB (2.7 KB with Closure), dynamic component factories no longer force massive maps, and dependency injection compiles to small factory functions. Locality enables incremental builds and shipping precompiled libraries, and internal testing runs across hundreds of Google apps for compatibility.
AI-written summary · about
chapters (37)
- 0:00Intro
- 3:45Simplification
- 4:26Goals
- 5:36Previous Architectures
- 6:01Template Example
- 7:20Template Compiler
- 8:52View Engine
- 9:23View Engine Template
- 9:45What is Ivy
- 10:44How does Ivy work
- 12:09Ivy template
- 12:58Ivy instruction set
- 13:29Change detection
- 13:47Authentication Guard
- 14:38Factory Function
- 15:52Benefits Goals
- 16:34Treeshaking
- 17:17Unused Code
- 18:20Tree Shakers
- 20:15Tree Shake
- 21:28The View Engine
- 22:08Dynamic Component Instantiation
- 23:27Component Factory Resolver
- 25:03Hello World
- 27:25Optimizations
- 28:08Incrementality
- 29:33Locality
- 30:39Inputs and Fields
- 32:09Binding
- 32:47NPM
- 33:21NGIF
- 34:19IV
- 34:54Builds
- 35:33Flexibility
- 36:53Hybrid Applications
- 38:32HighLevel Components
- 39:51Summary
