How do Vue, Angular, and Svelte handle deep prop mutation re-rendering?
WHAT IT TESTS: Deep reactivity vs zone-driven dirty checking. ANSWER OUTLINE: Vue and Svelte detect nested mutations via Proxies; Angular default re-renders via Zone.js, but ngOnChanges misses it since the reference is unchanged.
WHAT IT TESTS: Whether you understand deep reactivity versus Angular's zone-based dirty checking and reference equality. ANSWER OUTLINE: Vue wraps props in reactive Proxies, so nested mutations precisely trigger child updates. Svelte's $state runes use Proxies for deep reactivity, detecting pushes and property mutations automatically. Angular default runs full tree checks after any async event, meaning the child view re-renders, yet ngOnChanges does not fire because the input reference is unchanged.
Read the original → svelte.dev
- #vue
- #angular
- #svelte
- #change-detection
- #reactivity
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.