Why differences between t3 App and tRPC starter app?
I'm relatively new to using React and quickly adopted Typescript and NextJS having been inspired by Theo, Jack Herrington and Dave Gray. I converted a blog type web using php into one using NextJS 13 and I've now done a version using the T3 App; so I'm moving forward in my learning. I must say I very much like the app version of nextjs to the pages version and so am keen to keep an eye on T3 version in case that changes to the now production ready nextjs 13.
In checking versions I followed a link to the tRPC github site where I notice there's a version using nextjs, prisma, so I installed that version and the latest T3. I notice there are quite a few differences one of the most striking is the differences in directory structure of the server/ directories. Some files have the same code but are named differently, other files are different in name and content or implementation (server/api/root.ts vs server/routers/_app.ts in t3-app and trpc-prisma-starter respectively).
Is T3 and tRPC only loosely connected or is tRPC simply moving faster than T3? Can anyone point me in the right direction please?
1 Reply
So, from what I understand, you're worried about the different naming scheme from create T3 app, and the template provided by tRPC?
create T3 app is a CLI tool, which not only uses tRPC but other things like nextauth, Prisma, tailwind CSS.
as for the App router tRPC is not stable with next 13
Keep in mind tRPC it's just a part of create T3 app
You can opt out of it when setting an app up
Hope that helps but if you have any further questions just feel free to ping me and ask