Nice! This is the beginning of something awesome. It would be great if you can standardize methods/API that custom elements should have so that then people can install the custom element SSR as a lib. A next step would be that it can support async network requests at any level in the DOM tree, not just the root route component. There would need to be a way to signal that the tree has finished loading, or something.
But yeah! SSR isn't limited just to libs like React, and you're proving it! Someone just needs to implement it, and now you have! Nice work!
Nice! This is the beginning of something awesome. It would be great if you can standardize methods/API that custom elements should have so that then people can install the custom element SSR as a lib. A next step would be that it can support async network requests at any level in the DOM tree, not just the root route component. There would need to be a way to signal that the tree has finished loading, or something.
But yeah! SSR isn't limited just to libs like React, and you're proving it! Someone just needs to implement it, and now you have! Nice work!
Also check out this interesting article! medium.com/@mlrawlings/maybe-you-d...
It's be sweet to achieve what Marko has SSR-wise, but with Custom Elements. The syntax is nice sugar too.