The Angular Q&A covered Incremental Hydration and the progress on modernizing testing tools. linkedSignal
and resource()
will be the first of the long-awaited utility functions for Signals.
Q&A Session
Last week, the official Angular YouTube channel released a video on Incremental Hydration, a feature aimed at boosting the initial loading performance of Angular applications, particularly for those focused on SEO.
Mark Thompson from the Angular team hosted the video and the Q&A session later that week. Jessica Janiuk, one of the key developers behind Incremental Hydration, joined the session with Jeremy Elbourn and clarified that Incremental Hydration, unlike React Server Components, allows any Angular component to become hydrated.
During the Q&A, Jeremy addressed a few key topics. He noted that while utility functions related to state management are in development, there are no plans for anything on the scale of NgRx.
Regarding testing, Jeremy mentioned that the work on the official Jest support, which was announced with Angular 16, will resume next year.
However, Jasmine/Karma is currently working well, and there are other priorities for the team.
Utility Functions linkedSignal()
& resource()
Two new PRs for utility functions landed: linkedSignal()
and resource()
/rxResource()
.
linkedSignal
creates a WritableSignal
, which can also change its value depending on another, linked Signal.
resource()
, paired with rxResource()
, is designed for handling asynchronous tasks like HTTP requests. It's unclear whether this is the "signalized" successor to HttpClient
or simply a foundation layer for future updates.
Both Enea Jahollari and Matthieu Riegler have written articles covering these upcoming features.
Community Content
For more, you can watch the Angular Autumn Camp recordings, last year’s ng-Poland sessions, or read Armen Vardanyan’s latest article on common friction points in Angular.
Top comments (0)