Dynamic components in multiple crates

[Nebdir]

I got the idea of having multiple was modules containing different components that can be loaded on demand.

Is this possible using yew? I've read that one optimization is taht you split your code to reuse on multiple pages. ref
I like this, but wondered as it is possible to have a rust wasm app load another wasm component. ref

My vision is that a component is declared in a crate that gets compiled to a wasm module. Lets call this one Clock
In the main app i declare Clock to be a external component, that is on the server with the location static/clock.wasm. Upon rendering tha main app should load static/clock.wasm and render that component.

What im currently missing, is that i m not aware how the components are renderd or somehow placed in a wasm file, so that these components maybe dynamic loadable. Can someone give me me a hint if this is possible or blocked by something?

[WorldSEnder]

Loading another wasm module is complicated by several facts presented by wasm and ABI concerns that are currently very hard to work around.

1. While it is theoretically possible to load two wasm modules to share a common memory space, this is not well supported by build tools. Usually you get javascript wrapping code that has instantiates individual memory instances. The main reason for this is the lack of support for dynamic linking. As a consequence, these different modules will have to explicitly communicate by message passing. This compounds with
2. You might expect a compiled module/component to be loadable from your app component even if these were compiled with different compiler versions, or even minor versions of yew. What this means is that some sort of stable ABI would be necessary that is understood by the loaded and the loading component.
3. Also further complicated by 1., splitting wasm modules would necessarily duplicate runtime code (at least parts of std, and panic related code but most likely further shared code) since you can't have a "shared" third module that is loaded in by all (again, no dynamic linking).

There is, however, a solution that works. If you encapsulate your components as a web components. See also #1666 which covers a few of the finer points, as some rough edges have been worked out.