Sounds like you are being biased here. I mean, if you think vite-plugin-ssr to be rigid, then Next.js should feel like a 2sqm prison cell to you ;-). If you w

Sounds like you are being biased here. I mean, if you think vite-plugin-ssr to be rigid, then Next.js should feel like a 2sqm prison cell to you ;-). If you want more flexibility than vite-plugin-ssr then use Vite's native SSR API. Whereas with webpack: good luck with 1. using two webpack configs (one for Node.js and one for the browser), 2. synchronising between these 2 webpack configs, 3. implementing server-side HMR; it's incredibly painful and can cost you many weeks of dev time... whereas Vite's SSR API does all of this for you for free. Sure, things are early stage, but saying that webpack is "definitely" on top for SSR is wrong in virtually any possible way.