How do React Server Components fit into the T3 stack?
Hey there,
I'm considering the T3 stack for my next project (basically a dashboard full-stack web app), because I like the idea of using NextJS as a full-stack framework. It seems to make more sense in my use case than having the front-end and the back-end as two separate projects.
I'm just really confused about tRPC, RSC, and how they fit together. React Server Components are now the default in NextJS, so does that mean that tRPC is no longer necessary?
Curious how you guys resolve this question when starting out your T3 projects now.
1 Reply
T3 stack is amazing. I am personally just gonna build out stuff in this until the wheels fall off. Trying to navigate the constant changes with the SC and all the packages that are not yet compatible is a real doozy. I feel like this is a very safe zone to be in right now. I can build production-ready apps and launch them. The same way people have been doing it for years.
The announcement of the SC being stable does not suddenly make TRPC useless. I was in the same boat as you a month or two ago deciding whether to pull the trigger on t3. So happy I did, I love it.
Very opinionated way of doing things that helps you avoid the shitstorm of possibilities with all this bleeding edge tech. Still messing around with the SC and built some projects with them.. But personally gonna hold off for a while. I highly recommend it.
I resolve these issues by not trying to on the latest of the latest, comfortably riding the crest of the tech wave rather than trying to be right on the bleeding edge all the time. Production ready, battle tested apps that make dollar is my endgame.