Angular BatScanner
summary
Angular BatScanner hooks into Angular's compile meta resolver to auto-instrument component lifecycle hooks and record change‑detection events, revealing the top‑to‑bottom then back‑to‑top check order. It builds a flame‑chart style stack of component checks, uses hooks into CompilerMetaResolver and a Chrome extension with rAF/idle scheduling to capture events without blocking digest, requires two small bootstrap injections to export traces, currently approximates per‑component timing and needs better aggregation and precise child‑check timing.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 3:44Introducing Angular BatScanner
- 7:22How BatScanner hooks into Angular
- 10:17Building the Chrome DevTool extension
- 13:09Limitations and future improvements
- 16:03Conclusion and Q&A








