For those who may not know, here's a similar library: https://github.com/CanopyTax/single-spa https://github.com/CanopyTax/single-spa I'm glad to see two solut

For those who may not know, here's a similar library: https://github.com/CanopyTax/single-spa https://github.com/CanopyTax/single-spa I'm glad to see two solutions out there, because there's a lot of variety in how this problem can be solved. For example, single-spa recommends (but does not mandate) using import maps [0] using SystemJS (to get better cross-browser support) The idea is, each application says they want 'react-dom' or '@angular/core', and it is resolved to a URL. However, if applications are built expecting, say, different versions of dependencies, a naive approach to import maps won't work (e.g., the import 'react-dom' is requested-- how do we know which version to serve?). At my employer, we take each frontend application and transpile to ES Modules and then combine via webpack. It's not what's recommended in Single SPA, but it greatly simplifies the deployment architecture for us. We don't have to worry about hosting a CDN that can resolve import maps, everything's just in the bundle.