Matthieu Riegler explains Angular’s new DOM synchronization process, replacing modern change detection. Meanwhile, the standardized Observable lands in Chromium 135, influencing RxJS 8’s release.
DOM Synchronization
Matthieu Riegler is a member of the Angular team, and his articles always provide deep insights. This time, he covers the synchronization process, the new term replacing change detection. He explains the two phases of creating and updating the DOM and how this translates into real code.
He also touches on dirty marking, which determines whether a component should be checked for synchronization, and draws a comparison to the Virtual DOM, the rendering approach used by React.
Future of NgModules
Older Angular applications often have NgModules scattered throughout the codebase. At TechStackNation, Alex Rickabaugh, lead of the Angular framework, suggested that migrating to standalone components would be a good idea. Modern features like defer and the upcoming selectorless will be standalone-only, but NgModules will not be deprecated.
Standardized Observable
Signal-based Angular applications rely far less on RxJS than non-Signal-based ones. However, RxJS is not deprecated—in fact, Observables are becoming a web standard and will ship in Chromium 135, scheduled for release on April 1st.
According to Ben Lesh, the maintainer of RxJS, RxJS v8 was on hold until this point and will now incorporate the standardized Observable.
Observable API Design Doc - Google Docs
docs.google.com
Outlook httpResource
If everything goes according to plan, Angular 19.2 will be released this week. The highlight feature is httpResource, and if you want to get a head start, Cédric Exbrayat has already published an article covering it.
A guide to HTTP calls in Angular using httpResource() | Ninja Squad
Angular 19.2 introduces a new function called httpResource(). Let’s dive in!
blog.ninja-squad.com
Top comments (0)