Allow on-demand upgrade from static html to js components (islands)

[ibotty]

The idea is described here https://jasonformat.com/islands-architecture/

There was a comment on reddit asking for the same thing.
https://www.reddit.com/r/rust/comments/ouqfg3/new_tokio_blog_post_announcing_axum_web_framework/

[lukechu10]

This is currently blocked on #81. Right now, the original DOM is destroyed and recreated.

It would be nice if we could provide support for https://github.com/snowpackjs/astro. That should provide quite a bit of heavy lifting for supporting this.

[mash-graz]

is this issue still blocked by some fundamental requirements or already solved by #240 or similar improvements?

support for astro would be indeed an extremely useful feature!!

i really would like to use sycamore based web components as islands in this kind of more common markdown based and framework agnostic SSG workflows in my daily work instead of just watching the progress of another competing but again incompatible revolutionary rust web framework. ;)

[lukechu10]

i really would like to use sycamore based web components as islands in this kind of more common markdown based and framework agnostic SSG workflows in my daily work instead of just watching the progress of another competing but again incompatible revolutionary rust web framework. ;)

If what you mean by web components is this: https://developer.mozilla.org/en-US/docs/Web/Web_Components, sycamore should already be capable of creating web components albeit with some (a lot) of glue code. Eventually we could have a crate like sycamore-element that removes some of the boilerplate for this.

A problem with wasm based frameworks is that they do not support code splitting. Unfortunately, this means either downloading all the components used or creating a separate bundle for each component, at the expanse of duplication of library code. Hopefully this can be solved by rustwasm/team#52