T3 Stack for Large-Scale Project: Pros and Cons?
Would you prefer using a T3 app for a full-stack project with numerous tables and numerous CRUD operations? As you know, T3 has a monorepo architecture. I've read some things about monorepos slowing down the TS server as they grow. I'm using Drizzle and exporting select and insert types for each table. I'm also creating Zod schemas for all endpoints and inferring and exporting types for all these schemas.
Since I'm at the beginning of the project, I welcome any suggestions you might have.
2 Replies
for cons you can check this video, maybe some stuff is out of date but you can get the idea
Theo - t3․gg
YouTube
Flaws of the T3 Stack
I love my stack. It's the worst. This is a video all about the weaknesses of my stack. Prisma, NextJS, Next-Auth, tRPC, Vercel, Tailwind, and more.
CHECK OUT THIS STACK https://github.com/t3-oss/create-t3-app
ALL MY CONTENT IS FILMED LIVE ON TWITCH AT https://twitch.tv/theo
ALL MY BEST MEMES ARE ON TWITTER FIRST https://twitter.com/t3dotgg
ALL...