A security flaw in Angular Universal (SSR) has been found. The request for comments on control flow syntax and deferred loading was concluded. The Q&A session returned, introducing fresh material by Dmytro Mezhenskyi and Thomas Laforge.
SSR Vulnerability
Kicking things off is a security alert. For those using server-side rendering in Angular 16.1.0 or 16.1.1, it's time to move up to version 16.1.2. The culprit lies within Angular Universal's dependency, Critters, which falls prey to cross-site scripting.
Closed RFC
The RFC centered on deferred loading and template control flow syntax has wrapped up. It drew over 600 comments, and those responses mattered. The Angular team now has to pick a preferred syntax, choosing between an at Symbol or a single brace paired with a hash.
https://github.com/angular/angular/discussions/51241
Template Challenges
Alex Rickabaugh, who leads the Angular framework, shared some behind-the-scenes details. He outlined the hurdles the team encounters within the template domain.
One instance involved importing a component twice, and another touched on enhancing content projection.
https://www.reddit.com/r/Angular2/comments/15enffo/comment/jue6dlv/
Angular Q&A
The Angular Q&A stream returned after a two-month pause, hosted by Mark and Jeremy from the team.
A large number of questions came in, with a strong focus on Signals.
Overall, little was new, save for one point: the team is exploring enhancements to asynchrony through Signals.
Directive Composition API
A fresh video by Dmytro Mezhenskyi went up on the Decoded Frontend channel, covering the Composition API that’s been available since Angular 15.
share/shareReplay
A fresh piece by Thomas Laforge breaks down what sets the RxJs operators share and shareReplay apart.
On top of that, Thomas is behind the Angular Challenges—a set of hands-on exercises worth exploring.

blog.angular.dev