What is Angular Ivy's 'locality' and its benefits over View Engine?
Tests Ivy's per-file compilation model. Locality compiles decorators to static properties without global knowledge, except components need their NgModule scope, speeding builds and tree-shaking.
This tests your grasp of Ivy's move away from View Engine's global analysis. Locality means decorators compile to static class properties using only per-file metadata, without whole-program knowledge. The exception is @Component, which needs its declaring @NgModule's selector scope to generate ɵcmp. Benefits include eliminating .metadata.json sidecars, faster incremental compiles, and improved tree-shaking because definitions are self-contained.
Read the original → github.com
- #angular
- #ivy
- #compiler
- #locality
- #view-engine
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.