Just want to say well done. I’ve played with this with Tamagui[0] and I’d love to see this stack continue to develop.<p>Specifically, I think there’s a rare window of opportunity to replicate the new Expo router file system routes exactly in vite and build the holy grail of universal stacks.<p>I forked Hydrogen a month back or so just to get a feel for RSC and potentially how it’d work with native. Came away with huge positive impressions on Vite in general (and a vite stack that works nicely[1] with the Tamagui optimizing compiler fully working[2]).<p>Would love to collaborate towards this ideal setup with anyone competent, get in touch or I’ll ping in the discord.<p>There’s huge wins to be had at that level of vertical integration I think we haven’t touched yet.<p>[0] <a href="https://tamagui.dev" rel="nofollow">https://tamagui.dev</a><p>[1] <a href="https://github.com/tamagui/tamagui/tree/master/apps/site-vite" rel="nofollow">https://github.com/tamagui/tamagui/tree/master/apps/site-vit...</a><p>[2] <a href="https://tamagui.dev/docs/intro/compiler" rel="nofollow">https://tamagui.dev/docs/intro/compiler</a>
There's a fairly good and thorough comparison between vite-plugin-ssr and NextJS here: <a href="https://github.com/brillout/vite-plugin-ssr/issues/158" rel="nofollow">https://github.com/brillout/vite-plugin-ssr/issues/158</a>
Really interesting! How would you say it compares to Astro[0]? Astro is currently either all-SSG or all-SSR, but this quarter they're working on configuring that per -route.<p>[0] <a href="https://astro.build" rel="nofollow">https://astro.build</a>
Wowowowow thanks for your efforts behind this!<p>I’ve integrated vite with a rust backend[1] and so many people have asked me how I managed to achieve SSR because they equate SSR with render+hydrate but it’s really just classical SSR. I think I can finally make their dreams come true because of this.<p>[1] <a href="https://github.com/Wulf/create-rust-app" rel="nofollow">https://github.com/Wulf/create-rust-app</a>
What are the differences between this and the ssr in vite?<p><a href="https://vitejs.dev/guide/ssr.html" rel="nofollow">https://vitejs.dev/guide/ssr.html</a>
I am a big fan of vps. Brillout had some great ideas in this space, check out his other project Telefunc and Stem to see what I mean.<p>Things like the Enhance framework or Astro would be trivial to build with vps, especially once there single file page proposals get built.
I'm really liking it so far and have been using this in production for the landing (and soon the blog) page at <a href="https://devclad.com/" rel="nofollow">https://devclad.com/</a> using SSG.<p>Had some issues running the SSR api function on Vercel, though. Probably something to do with the the assets/ being specified in the wrong directory.
First and foremost: This looks great! I like the APIs, its a very next like experience, and I think the way you are handling fetching data is better than getInitialProps or getServerSideProps simply because it seems less limiting in approach.<p>Next.js is really being held back by webpack IMO and they would do well to convert to rollup / vite I think. This, Hydrogen from Shopify et. al. are proving webpack doesn't have the best future I think.<p>All that said, there is one thing about community solutions like this I worry about:<p>I know as long as I'm paying money to Vercel, I have support with Next.js and it will (in all realistic likelihood) be that way for years.<p>With community backed frameworks, there is no way that, say, this won't become unmaintained.<p>For all the possible warts Vercel / Next.js may or may not have, I think as a business building on top of these things, its important to take this into consideration. I'd rather not switch my SSR framework out from under my feet in 18 months.
Thanks for your work, this is what I am looking for. I have been looking for NextJS alternative since I have a tough time deploying to Cloudflare. I don't know why this never came up in my search results even though I digged beyond the 10th page of search result on many search.
Cool! I think with the popularity of next, SSR react frameworks are here to stay. My biggest gripe with next is how much I dislike vercel, currently looking at alternatives.<p>But nicely done! I'll play around with it