Summary
In this chapter, you learned how to create appealing SPAs using individual plugins, which are merged into a single coherent web application. In contrast to the classic plugin architecture, these modules may get privileges and responsibilities that are on the application level.
As with the SPA composition before, you saw that user interaction is meant to be quite high. However, unlike with SPA composition, the user experience and developer experience are supposed to be smooth. While the internal complexity and tool reliance have increased, the major drawback is the dependency of the modules on the API defined in the app shell.
In the next chapter, we’ll dive deeper into runtime integration of micro frontends. In particular, we want to explore how we can efficiently share dependencies at runtime using modern mechanisms such as webpack’s Module Federation plugin.
