Can you imagine a future without zones?
summary
Demos show that Zone.js only triggers Angular’s change detection but is not part of it, and an app boots with Zone.js explicitly turned off by disables Zone.js in bootstrapping to prove clicks no longer update the DOM. Workarounds include injecting ChangeDetectorRef and calls detectChanges manually, and Ivy adds a nonblocking scheduling API — markDirty schedules change detection in the next VM turn. Example code runs live and the manual approaches work but cost developer effort and can increase change detection runs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:30Maxims story
- 3:40Demo
- 4:45Troubleshooting
- 7:40Disabling Zones
- 15:55Manual Change Detection
- 21:05Automatic Change Detection
related talks
25mCan you imagine a future without zones?
41mState of change detection in Angular and how far are we from Zoneless applications ?
30mNo Zone, No Problem - Building Angular Apps without Zone.js
01h 02mChange Detection, Zone.js and Other Monsters
37mGet ready to go Zoneless
01h 11mFully Zone-less — High-Performance Angular Applications in Post IVY
44mAngular 2 Change Detection Explained
33mMonitor the Angular application with Zone