After packaging and publishing to the server through vite-ssr build, the server has already sent the complete HTML+CSS+JavaScript to the client's browser (i.e. SSR). However, the client browser will re render the entire interface. How can we avoid duplicate rendering by the client? After all, the server has already sent the complete HTML+CSS+JavaScript to the client, and the client's browser can directly parse HTML+CSS+JavaScript, so there is no need to perform client rendering (i.e. CSR) again.
Here is my server deployment code. Can you help me see why the client renders repeatedly? Is it a configuration issue with packaging or a deployment issue?
This is the file structure that I packaged through vite-ssr build
After SSR renders the complete HTML+JavaScript+CSS, it sends it to the client, and the client's browser renders it again, which is a waste of performance. I hope you can help me. Thank you very much.
Thank you for your excellent code that helped me!
After packaging and publishing to the server through
vite-ssr build
, the server has already sent the complete HTML+CSS+JavaScript to the client's browser (i.e. SSR). However, the client browser will re render the entire interface. How can we avoid duplicate rendering by the client? After all, the server has already sent the complete HTML+CSS+JavaScript to the client, and the client's browser can directly parse HTML+CSS+JavaScript, so there is no need to perform client rendering (i.e. CSR) again.Here is my server deployment code. Can you help me see why the client renders repeatedly? Is it a configuration issue with packaging or a deployment issue?
This is the file structure that I packaged through![image](https://github.com/frandiox/vite-ssr/assets/106658444/f7484dae-5ee7-4163-a4b9-28be11c27953)
vite-ssr build
After SSR renders the complete HTML+JavaScript+CSS, it sends it to the client, and the client's browser renders it again, which is a waste of performance. I hope you can help me. Thank you very much.