Dies ist Beitrag 9 von 9 der Serie “Module Federation” The Microfrontend Revolution: Module Federation in Webpack 5 The Microfrontend Revolution: Module Federation with Angular Dynamic Module Federation with Angular Building A Plugin-based Workflow Designer With Angular and Module Federation Getting
This article shows an approach for using different frameworks and versions together. It also discusses the pros and cons.
With the introduction of Standalone Components, NgModules will become optional. But how to prepare for this future?
For the grouping of related building blocks, simple barrels are ideal for small solutions. For larger projects, the transition to monorepos as offered by the CLI extension Nx seems to be the next logical step.
Standalone Components make the future of Angular applications more lightweight. We don’t need NgModules anymore. Instead, we just use EcmaScript modules.
In diesem Tutorial lernen Sie alles über NGRX in Angular: Actions, Reducer, Selektoren und Effects sowie Debugging und Meta-Reducer.
Mit dem Angular Router simulieren wir verschiedene Seiten und etablieren eine Navigationsstruktur
In diesem Kapitel wollen wir unsere Lösung mit Boardmittel von Angular verfeinern.
Erste Komponente, die via HTTP Daten abruft und via Datenbindung darstellt.
Eine erste Angular-Anwendung
This time, we interviewed no one less then the international security expert Dr. Philippe De Ryck, GDE.
This week, I’ve interviewed my colleague and testing expert, Rainer Hahnekamp, about trends in the area of Angular testing.
Learn to build sustainable Angular architectures!
The goal of this article is to show typical pitfalls that come when using Module Federation together with Angular and strategies for avoiding them.
Combining Module Federation and Web Components brings several advantages. But there are also some pitfalls we need workarounds for.
The combination of Micro Frontends and monorepos can be quite tempting: Sharing libraries is easy while we can isolate domains using access restrictions and deploy them separately.
Module Federation uses SemVer by default and there are lot’s of options to adjust its behavior.
Module Federation allows loading plugins from other origins,
Loading microfrontends not known at compile time.
UMD bundles allow loading separately compiled and deployed microfrontends. This can be already used today together with default Angular applications and libraries.
With Module Federation we can use Angular and its router to lazy load separately compiled and deployed microfrontends.
Module Federation allows loading separately compiled program parts. This makes it an official solution for implementing microfrontends.
Defining an architecture is exciting. However, implementing it can also be boring. Automation with scaffolding is the solution.
Instead of loading all supported locales upfront, we can now load them on demand.