Rhywden

Well, downgrading only works in Windows as it turned out. As soon as I pushed the whole thing to production (which is a Linux server) I got a similar exception...

> It's also possible for it to be an upstream issue (something might have changed in ffmpeg itself) - have you verified that the issue exists regardless of the version...

The documentation on this is **very** incomplete. Particularly on how on Earth to convert, say, a "Fragment" to an "Element". I mean, we have the function "Snap.load()" which loads an...

Sorry, but "you have to do something" doesn't quite cut it. I also don't want to have to add some SVG elements just to get my existing SVG file to...

Well, that part I got working now, thanks to @matelich . However, I ran into a bit of a problem when I then tried to add another element to the,...

Okay, so I found a way to get things going. Works like this: You define your actions, state and reducers completely like normal on the `Client`. Then you create a...

> One way to initialize the client side store is to add a component in your client project that contains > > ``` > @rendermode InteractiveWebAssembly > > ``` >...

Yes, that's where I got it from.

> Are you talking about the new "static server side rendering"? > > If so, that's a stateless approach. The state of the page is determined on every render, so...

> It seems like some work is required to initialize the store once but in a way that both WASM and Server components can use it. Just to make it...