@Eiji I’m going to be looking at providing support for SPA’s (haven’t looked at what that would entail, if anything - I almost think that you could get by with one “master” component that’s injected into one view as-is in terms of what the library supports now, but it might be more reasonable to define a separate build process in case an SPA is the goal), and hopefully building out some small JS helpers to help with websockets on the Svelte side. I think the approach you suggest is interesting, and definitely worth exploring.
In terms of why use JS only partially - the library came about because I was designing a few “games” that were far too complex to make work using only LiveView, and that had to be scattered throughout the site, and Svelte seemed like the perfect tool for the job. Nonetheless, the site still benefits from being SSR’d, given the nature of the domain. That being said - I’m sure most of what I’m doing could be replicated in LiveView with enough sweat and tears, I just found that the moment I made the conceptual shift to working with Svelte for these small components, I felt much more productive and “in control” (granted, I’m also sacrificing the simplicity of keeping it all in Elixir).
