[X] None of them.
First of all, did you check your requirements against the problems solved by these frameworks / libraries and how they work? All of them are made for dynamically creating components and manipulating the DOM at runtime. Do you need to do so? For a website, the answer is NO most of the time. They are useful for web apps, though.
For websites, you usually want to support people, who disabled JS, people with screen-readers, bots which cannot use JS, etc. - there might even be legal requirements to support accessibility! Also, you usually want high performance and most likely low costs and low battery drainage on mobile. As a conclusion, write a static website, which is assembled at build-time, not at run-time (either on server or client). Reduce the client-js and try to keep the server from doing any calculations. Optimize all resources, which is way easier with static resources. Then upload your site and enjoy. It's greener, too, btw 🌻
Even for a big-scale website, going static is very viable and does not mean that you have to write out everything by hand and repeat your code like it's the early days of the internet. For example, if you need templating, I recommend using pug or handlebars, which can be used by most packers and results in the correct static html.