Ability to run multiple Blazor server / Web assembly apps in the same document (micro-frontends)

[javiercn]

It's interesting for us to consider running Blazor Server and WebAssembly applications in the same document as well as being able to mix them on the same apps. We've heard feedback that some people don't want to have some "proprietary business logic" on the client, and this offers a way to to do so. In the same vein, we can expect larger apps developed by several teams to run into conflicts on the versions used by their apps. Being able to run multiple blazor versions on the document, avoids this problem at the cost of increased app size.

UPDATE (from @MackinnonBuck)

We've opened #48032 to track the ability to have a single Blazor app that uses Server and WebAssembly components on the same page. This enables scenarios critical to the #46636 effort. It does not, however, include the ability to have completely separate Blazor app instances exist on the same page. That remaining work is what this issue tracks.

Source: #38128 (comment)

[jmezach]

This is also important for micro-frontend scenarios where one might have multiple "islands" of Blazor on the same page. For example, we're considering adopting single-spa to modernize our existing monolithic front-end into smaller micro-frontends and it would be great if there was a way to build some of these micro-frontends using Blazor.

[timeshift92]

hello, as one of way, after download wasm binaries swap server to wasm
https://github.com/jdtcn/HybridBlazor

and second for state machine between server and client using this case
https://github.com/servicetitan/Stl.Fusion