During the February Q&A session, the Angular team explained that it selectively re-renders only the DOM nodes that have changed, advised structuring projects by feature rather than by type, and simplified the usage of lifecycle hooks. In parallel, Manfred Steyer published a fresh article presenting Native Federation, an ESM-driven approach that serves as a substitute for Module Federation in Micro Frontend setups.
Q&A February
The recurring Q&A session with the Angular team happened again. This time around, the stream leaned heavily into coding, as Mark kicked off by building an Angular app from scratch, though questions were still part of the agenda.
When asked about how and when Angular re-renders components, Jeremy provided a crisp explanation—a handy one for interview prep: Angular skips re-rendering entirely, and instead, it just patches the specific DOM elements that shifted.
The conversation also touched on Angular project structure. Jeremy noted that the upcoming, revised style guide will push for feature-based folder organization. In general, most layouts work fine, but dumping everything into catch-all folders like "component" or "service" is discouraged.
Regarding lifecycle hooks, keep in mind that onInit signals all the component's inputs are ready, while afterViewInit indicates child components have their inputs set. In modern Signal-driven apps, the only hooks needed are afterNextRender, onInit, and onDestroy.
Jeremy also shared that he's gone through the resources RFC, which hints we might see it released soon.
Micro Frontends
Micro Frontends keep coming up in the Q&A sessions. Angular ships without any native tooling for this pattern, and for a long time, the team has hinted that an official write-up was in the pipeline.
That write-up has now arrived. On the official Angular blog, guest author Manfred Steyer delved into Micro Frontends—their definition, the hurdles they introduce, and various ways to implement them.
Module Federation, which gets backing from both Nx and Angular Architects, stands out as a widely adopted choice. Yet Manfred highlighted Native Federation, another offering from Angular Architects that closely resembles Module Federation in many respects.
What sets them apart? Native Federation pulls in native ESM-based files at runtime, whereas Module Federation leans on the bundler’s internals (currently webpack, with Rspack support on the horizon).