Is there official documentation for enabling React compiler with Tanstack Start and Vite ? @tannerlinsley
Do we just have to add babel-plugin-react-compiler to the Vite config and it works out of the box ?
Tanstack Start has released the Rsc support and it looks amazing.
I like the simplicity behind this new feature and the approach of streamed data seems to be the right way.
Once again, Tanstack stands out from Next.js.
#TanstackStart#NextJs#React
I migrated an existing Next.js project to Tanstack Start easily.
The ease and performance of Tanstack Start are incredible.
I don't think I'll be using Next.js again anytime soon, it’s abnormally over engineered.
#nextjs#tanstack#tanstackstart
@1nterlandi I used the Tanstack request context to pass the user information to all my routes. Hence I didn’t need, any client component to fetch the dynamic information related to the user.
@1nterlandi I started to use the cache component feature of Next.js 16, and it drove me crazy. I encountered a lot of difficulties with partial pre-rendering and client components, then I decided to switch.
@wineworm@tannerlinsley The craziest thing is that I migrated most of the project manually very quickly. Ex: Server action => server function. Middleware are also better handled with Tanstack you can them directly close to your routes. I’ve also removed all the wrapper around client components.
C'est décidé, je lâche Next.js pour passer sur TanStack Start. 🚀
Next devient trop complexe. Ils prônent les Cache Components mais c'est un enfer : problèmes d'hydratation à la pelle qui obligent à abuser des "use client"...
#TanStackStart#Nextjs#React#WebDev
🔥 Correntin a push en prod par erreur.
Le front est mort.
Je lui dis de faire : git rebase -i HEAD~1
👉 Maintenant il est bloqué dans Vim 😭
🎬 Épisode 3 de ma mini-série dev :
📺 https://t.co/zPpXSZ2PP1
#devhumour#git#vim#bugprod#cicd#fypシ#webdev#devlife