Given that van replace the whole tree each time a value changed, SSR for van is simpler. You run chrome server side, capture the DOM once van has finished its first execution and modify the HTML of the page to includes the new nodes.
Don't run chrome on the server for SSR, I beg you. That's a massive performance hit and scales terribly with all the memory usage.
In this case, you can do it on your CI as part of the deployment, so it's not that bad.
Sure that's doable if the site is static only. I was going off the SSR terminology which usually means the html is rendered at the time of request instead of built one ahead of time (SSG)