I have a Vue.js application working with Server Side Rendering (SSR) and then client side hydration and it works fine. I like to build isomorphic javascript and think that this is the way to the future.
But there is one more problem that I would like to solve. Here is a simple diagram:
First we check if we have a cached HTML response
If we donβt have a cache, we:
- Make server side render (SSR) for rendering HTML from vue.js application
- Then we save the cache
- and send a response to the client
- Where at this moment we mount the vue.js application and do hydration on the client side.
This thread works for me and works great. I would like to figure out how to take a step in blue.
If we have a cache, I would like to:
- Download html and just like hydration on the client side, mount the vue.js application and update the pieces of cached html, then it is unique only to the current user (i.e. account information, like, follow, etc.).
- send response to client
- then, as before, you need to moisten the client side to make the page interactive.
I did some research, and I did not find any server-side hydration information. I even looked into other isomorphic frameworks like reaction and angular 2 to see if they have a solution and cannot find it.
I am not against creating something like this, but I need a push in the right direction, therefore, if there is someone who is working on this species or has any suggestions, it is very appreciated.
source share