Jonathan Gelin's article on Micro-Frontends will quickly become a new reference in the field. Jeremy Elbourn, Angular tech lead, gave his opinion on the "production-readiness" of Signals.
Micro-Frontends and Import Maps
Micro-Frontends are quite a fascinating topic. Some projects need them, some want them but don't need them, and Angular doesn't officially support them.
Jonathan Gelin wrote an article giving you a holistic overview of Micro-Frontends, including when it makes sense and what kind of technologies we have now and in the past. For example, in Webpack, it was module federation; now, with Esbuild, we can say the browser natively supports it via import maps, hence the term native federation
Jonathan also touches on the challenges of setting up the development environment, integrating it into a CI, and our deployment strategies.
He ends by suggesting that Monorepostiories and Micro Frontends don't have to be contradictions, especially if your tooling, like Nx, supports that scale.
Q&A with Mark and Jeremy
The monthly Q&A session with Jeremy and Mark from the Angular team occurred. Jeremy, the Angular tech lead, tends to give quite clear and straightforward answers.
So when the question came up of whether we should already use Signals, his immediate response was yes. He explained the improved developer experience coming from the reactive nature, the possibility of derived values, and running side effects with computed and effect.
He also mentioned that Signals are still in developer preview because of the effect function. Jeremy emphasized the meaning of "Developer Preview again": It is a stable feature that allows the Angular team to introduce breaking changes within a major version.
Top comments (1)
Hi ng-news,
Your tips are very useful
Thanks for sharing