This took us too long, I'm sorry 

Next up: we've got some docs writing to do

Ey, it's Blonde Prime

Ayyye! I've been waiting for this. Thank you, Theo & team!

Whoop whoop. I've been using the old pages router T3 app as a reference and made my own app version. Glad I can compare the new T3 app to squash some of my bad practices.

Really awesome tech in the t3 stack! I’ve been using it recently to learn more about frontend, next, and that (I’m a backend developer). The setup is seamless and it gives you a lot of speed. Gonna star it right now!

julius is the one who is making the hard work

Actually started a new t3 project yesterday and noticed they now support app router Great stuff

You should add the serverAction wrapper that tRPC team made.

Can you speak to TRPC in larger apps? We are struggling to manage all the query invalidation without normalization like there is in Apollo GraphQL. Thanks!

thanks i was waiting for this.

Glad to see this finally coming out ! Seeing that the docs are not up yet, does anyone know why the _components folder is named like this ?

Fantastic job there! I was playing around with kirimase, since it promised to be roughly a t3 experience but with shadcn and drizzle and app router right off the bat. And while it's sorta true, it also introduced a bunch of boring stuff like separate service files. I hate the weird insistence on making an api route, and only putting return service.getAll(input); in it. I sort of get the point of services since you could reuse the fetch code in two places instead of actually calling the router since that apprently is slow if you do it too much, but since these functions are more often than not 2 lines long, you could just copy the code and not cry about it too much. Either way, looking forward to doing my next project with this. long time coming but finally here!

What’s the story with caching tRPC requests in RSC? Next cache invalidation via tags only works using fetch, right?

Great video! I downloaded the latest version of the T3 stack and I was wondering why was so different from you official 3h tutorial

Very noice🐢

Could you do a quick video about Arc and the extensions and features that you're using?

Finally! I waited so long for this. I prefer app router and was really sad that I couldn't use t3 stack with this directly

Based in nextjs, but still cool it's the first Typescript only framework to use the app router.

🔥

that hair man with the moustache combo wtf

I'm getting a issue with Hot Reload when using App Router. Whenever I save in the editor, the rendered page loses all styles for a brief second and then apply the css later. I'm using Tailwind.

I was working with App router for a while, and here the issues I faced. Framer motion animations doesn't work. Routing animations doesn't work. Page elements animation not working in production build. Cannot push url params changes without reloading the page. These small things really tarnish the developer experience and deliveries. Going to stick with Page routing.

I was scratching my head asking to myself why its giving json error at an arbitrary position and was searching for this video like crazy lol. Probably the only theos video i missed and it made me suffer. Now i can compare. Thank lord theo and all the great 266+ people

I just found out you created t3. Dammnnn

Curious why you put the db object in the tRPC context, anyone know why?

I know you built your company with t3 stack, but do you think there are some freelance and saas scenarios that could use rails as a valid solution? or do you think if rails is a valid solution for a project, then t3 would also be valid and better than rails? thanks in advance. i'm looking to move into doing freelancing and did rails in the past so was thinking of using that but i feel like the t3 stack might have things i don't know about that will make my life easier.

FINALLY!!! 🎉

theo this is been happening to me everytime i run bun run dev on create t3 app that i get global.css error. i have tried this on windows with node 18(windows) with npm, yarn, pnpm, node 20(kubuntu) with bun which is installed day before yesterday with all the fresh installs no cache... yet i get the same error

he's back from begas

Well, now im excited to use t3.

Glad pages router is still being supported. I don’t feel ready to move my major projects to app router yet. Glad there’s Drizzle support now too, I prefer to Just Write SQL™️ but if I’m gonna use an TS ORM, Drizzle, despite its issues, is the one I will use.

Why still on react-query v4? Can’t v5 be used yet?

Sweeeeeet

what's the name of the browser you're using in the video?

I thought I'd give this a whirl. I have quite a large prisma schema, lots of relationships, and some data stored as json. Manually typing all these zod types was a pain. Decided to try zod-prisma-types and use those. My editor is freezing/dying, eslint keeps crashing, using trpc breaks static rendering also. I can see why some people like it, but I'm feeling it's very meh

I am not getting auto reload on dev server on the windows :(

We need clerk auth docs.

Hi, can someone please help me to understand how do we cache data using serverside components with this app router and t3 stack?

LFG

1 database for all the projects? irs okay for personal projects, but for customer facing apps its ideal to keep seperare dbs

What is this browser name?

Why are your thumbnails always like that? 😲

I miss internationalization

i see that its not ready.

as much as I love Theo and I'm like a hard core fan of him. I have to say that Kirimase (with only 9 contributors) does exactly what T3 does but much better.... more libraries support, and a codegen tool for a ruby on rails feel... once using kirimase I don't know to go back to T3...

lfggg

I think App router sucks. Not because of the features, but the decision to split Next.js "in half", meaning we will see a lot of companies using Next.js, but with projects in the old fashion Pages folder and others with App router. You basically need to remaster the framework you already knew. This sucks. This makes me doubt if its a good idea to invest my time learning this framework. If they launch a third "router" with totally new documentation, Im gonna throw myself out the window.

hey dude big fan here but please do some push ups and drink some milk

uff sounds very much like framework/ tool stacking which killed Java

nice , but this is really awful. it's like the backend that only an ux developer would do.

best stack ever

After 7 years of frontend development and working with Angularjs, Vue, React Nuxt, Next, Svelte etc... I feel everything is getting complicated more more. the only one that feels better was sveltekit e2e type sfaty without all these headaches... and simple, but it is also going under some new changes which maybe going toward react ...