Here are some commonly asked questions about
We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.
If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our Discord↗ and ask for help.
Although the resources listed below are some of the best that exist for the T3 Stack, the community (and Theo↗) recommend that you just start using the stack and learn along the way by building with it.
If you are considering
create-t3-app, chances are you might have already used some of the parts of the stack. So why not just dive in head first and learn the other parts while you build something?
Now, we realize this path doesn’t work for everyone. So, if you feel like you’ve tried the recommendation and would still like some resources, or you just aren’t confident doing it by yourself and/or feel overwhelmed by the stack, checkout these awesome tutorials on
- Build a full stack app with create-t3-app↗
- A first look at create-t3-app↗
- Migrating your T3 App into a Turborepo↗
- Integrating Stripe into your T3 App↗
- Build a Twitter Clone with the T3 Stack - tRPC, Next.js, Prisma, Tailwind & Zod↗
- Build a Blog With the T3 Stack - tRPC, TypeScript, Next.js, Prisma & Zod↗
- Build a Live Chat Application with the T3 Stack - TypeScript, Tailwind, tRPC↗
- The T3 Stack - How We Built It↗
- An overview of the create T3 App (Next, Typescript, Tailwind, tRPC, Next-Auth)↗
As per T3-Axiom #3, we take typesafety as a first class citizen. Unfortunately, not all frameworks and plugins support TypeScript which means some of the configuration files have to be
mjs) depending on what’s supported by the library it is used by. Also, all the
js files in this project are still typechecked using a
@ts-check comment at the top.
We have decided against including i18n by default in
create-t3-app because it’s a very opinionated topic and there are many ways to implement it.
As per T3-Axiom #2, we love bleeding edge stuff but value stability, your entire router is hard to port, not a great place to bleed↗. While
/app is a glimpse into the future↗, it’s not ready for production; The API is in beta and expected to have breaking changes.
For a list of supported, planned, and worked on features in the
/app dir, visit the beta Next.js docs↗.