4 ms·
Have you seen SvelteKit's source code? It looks like a toy project. [1] vite-plugin-ssr can't even be integrated with Vue Router (I saw you're working on deep
by eliseumds 5y ago
Have you seen SvelteKit's source code? It looks like a toy project. [1]
vite-plugin-ssr can't even be integrated with Vue Router (I saw you're working on deep integration though). They're both very rigid, early stage endeavours. [2] What happens, for ex, if you used nested lazy components in those pages, are they going to be included in the server render as well?
I mean, fair enough that there are people trying to do better, but it's extremely hard to find the right abstractions for such complex builds and Webpack is definitely on top here.
[1] https://github.com/sveltejs/kit/blob/5c2665ff2280947a2fc600128fe34fb3427b8609/packages/kit/src/core/create_app/index.js https://github.com/sveltejs/kit/blob/5c2665ff2280947a2fc6001...
[2] https://github.com/brillout/vite-plugin-ssr/blob/master/src/plugin/importer.ts https://github.com/brillout/vite-plugin-ssr/blob/master/src/...
- brillout 5y agoSounds 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.