Jonathan Gelin's piece on Micro-Frontends is set to become a go-to resource in the space. Angular tech lead Jeremy Elbourn shared his take on how close Signals are to being "production-ready."
Import Maps and the Micro-Frontend Landscape
Micro-Frontends remain a compelling subject. There are teams that genuinely require them, others that desire them without a real need, and Angular itself offers no first-class support.
Jonathan Gelin's recent article delivers a broad survey of Micro-Frontends—covering when they are appropriate and the technologies that have been used historically and are available today. With Webpack, the solution was module federation. In the era of Esbuild, the browser's native support through import maps gives us what is now called native federation.
Beyond the architectural patterns, Jonathan addresses the practical hurdles: configuring the local development setup, wiring things into a CI pipeline, and deciding on deployment approaches.
His closing argument is that Monorepositories and Micro-Frontends don't have to be mutually exclusive, particularly when your tooling—such as Nx—is built to handle that level of scale.
A Conversation on Q&A with Mark and Jeremy
This month's Q&A session brought together Jeremy and Mark from the Angular team. Jeremy, serving as the Angular tech lead, is known for his concise and direct responses.
When asked whether Signals should be adopted at this point, his answer was an immediate yes. He highlighted the enhanced developer experience that stems from the reactive model, the ability to define derived values, and the way computed and effect enable side effect management.
He did add a caveat: Signals remain in developer preview, primarily due to the effect function. Jeremy clarified what "Developer Preview" really means—it's a stable feature state that gives the Angular team the flexibility to make breaking changes within the same major version.