3 ms·
Wait upon quick glance Vite doesn't come with SSR support ... ? Yea guess I'll stick with NextJS
by jdthedisciple 3y ago
Wait upon quick glance Vite doesn't come with SSR support ... ?
Yea guess I'll stick with NextJS
- ironmagma 3y agoSSR support is only needed for public-facing websites that will undergo some kind of search engine indexation. For most apps this is not necessary since most apps are not accessible publicly.
- verdverm 3y agoNextJS does more than SSR, like determining routing based on directories and making React Server Components and Actions so simple it's hard to not choose NextJS They've removed a ton of pain from full stack React/JS/TS
- ironmagma 3y agoOK, but on the other hand I've heard from someone who worked at a startup that unnecessarily chose NextJS despite no requirement, and it really held back the organization for the rest of its existence, limiting velocity. Simple things like fetching queries become harder due to the split lifecycle. Relevant HN thread: https://news.ycombinator.com/item?id=36472166 https://news.ycombinator.com/item?id=36472166
- verdverm 3y agoYeah, you definitely buy into a paradigm and ecosystem that has its own flaws. It's all tradeoffs and right for for sure. My new project requirements for well with NextJS. I was mainly pointing out that there are a number of benefits for the drawbacks.
- moon_moon 3y ago[dead]
- romanhn 3y agoI built a React SSR app on Vite using Vike (https://vike.dev https://vike.dev), it worked well enough for my simple needs. Best part was I was able to easily reuse a bunch of components from the primary React SPA app that lives side-by-side in the same project without needing to buy into the "Next.js way".