Thanks for the resources, Wouldn't rehydrating the specific page which uses web component eliminate the need for explicit SSR support in the JS framework and thereby it comes down to whether the framework has good support web-components or not in the first place?
> Wouldn't rehydrating the specific page which uses web component eliminate the need for explicit SSR support in the JS framework
Erm.... No. If you don't have SSR then it doesn't matter if it's web components or not: they will be instantiated at runtime.
> it comes down to whether the framework has good support web-components or not in the first place?
All of them have decent support for web components (at least for "consumption").
The reasons they don't support them as a foundation (and at most emit web components if you tell them to) is that they don't want to deal with all the stuff like no SSR support, the need to still have all the layers above for things like lazy loading, progressive enhancement and a whole laundry of issues that none of the non-web-component frameworks have: [1][2]
