Видео

Great video. Thank you for the video.

This is gold my friend! Excellent video!! This mindset make PRs a training tool, so people can use PRs a information that they can learn from, even in other teams.

Another problem is: if you changed code and it uses another 3rd party library or just start using just another cal, of the 3rd party library, then you need to review the library also. Most people consider it as a back box working correct, but it isn't rue.

yesss

Can confirm, the team loves chris now I know how to make them love me!

Great video, and I think there is an even deeper point here. Empathize with the needs of your team. I have been in projects where communication was not done through code review. Do what you say apply. Well, directly not, but indirectly full on. At some point somebody looked at my stuff as well, and I could have done way more to make their life much easier! Thanks for the pointer to think into this direction. I like especially the idea of pictures about design decisions / changes, will think about how I can incorporate that into my work.

I'll be brutally honest here; if someone ever submits a PR for a project and includes a video with narration I'm just going to reject the PR outright.

Cool! But I think we should start small. How can I make my family love me?

what an amazing, to the point vid, thanks cj

Amazing vid

That's what exactly I was looking for. Thanks! One question, I don't see any 'use client' directive on your code and useState is supposed to be used only under 'use client' as far as I know. How did you do that?

It would be great if you done a video to explain how trpc works with nextjs react server components (i.e. when using .query() instead of .useQuery()). I intend to keep using trpc for the forseeable so i can build out a mono repo of all my applications with different clients that share the same backend / auth / types.

Great video thanks! I've been using ct3a to build all my companies applications but now have a good bit of confidence of how all the trpc magic works. Will be making some middlewares this week!

That thumbnail is wild man. Lmao

Brilliant video. Very glad to have found this.

This is a great explainer and helps me understand t3 app structure much better, but would be a bit nicer if we had access to the github source code you shared here so we could look at the files ourself to understand better. Thanks!!

thank you a lot. This is incredibly helpful. Videos like yours enable me to move forward in this field of programming. Going through all of this only with the tRPC docs would have probably taken me weeks or made me quit :D

Thanks man! This really help me out

Really good video! It's quite hard to find software engineering videos that are not code tutorials, and actually talk about advanced stuff. I'm starting to contribute to open source and this video helped me understand how to do it effectively and how to progress. Thanks

I am still wondering how TRPC manages to share types between different codebases say a simple react SPA (not Nextjs) and and express server. How is the library able know about the code in other other codebase ? Is it just that we rely on zod to do checks on both side ? that way we have to remember zod object schema - but I never saw it happening. So still wondering...

You are amazing! Thanks to you, now I can statically generate all the dynamic routes that have fixed content! BTW, I did land on that page at some point! 😂

trpc is just another patch for nextjs's missing feature e2e typesafety. I invite you to Sveltekit.

Really helpful! Thanks!

Thanks for the explanation! Really help me to get better understanding of TRPC flow in 20 minutes, keep it up 🔥

Thankyou

Good stuff!

Thanks Chris for explaining all of this. Your video touches on many topics, but lacks timestamps, so I wrote them down: 0:48 - Separate common logic into it's own functions 3:14 - How to structure your project How to call tRPC procedures from getServerSideProps: 5:05 - createCaller() 5:33 - just call an extracted function (see 0:48) tRCP calls with dynamic inputs (ex.: from query string): 6:15 - with initialData 7:35 - with createServerSideHelpers + dehydrate (aka createProxySSGHelpers in older versions)

Will it be in 1080p? Cant really see the code(

Ooh I’ll be watching this through its entirety! Excited for this :)

This was really helpful. Subscribed

Super helpful! Reading docs and posts is one thing but for those who are new to tRPC and web dev in general, having someone to walk you through the logic and code really helps the understanding. Thank you for making this!

we need you

this is really great! Well explained, I learned so much. exactly what I was looking for thank you. Only your sketch is so small and hard to read. But regardless of that keep it up man!

Is it possible to do a DB check in prisma with the middleware, I basically need to check if a user is authed and also DOES exist in the database

Can you use trpc without transpiling like an environment ts is not used, jsdoc instead or build step/bundler/transpiling is necessary? For example, you can use zod with jsdoc, is it the same story for trpc?

This is awesome. I’ve been using tRPC for a personal project and also a work project for a couple months now and feel much more confident in my knowledge of what felt like magic at the beginning. I hadn’t learned much about middle ware and now have lots of thoughts on simplifying repetitive checks in some of my procedures.

amazing tRPC explanation! thanks for your time and that great video!

Why first example isn't blocked on page load while last example is blocked until all server components fetched? Is it because server components were hidden inside of client component ?

Thanks for this video, I updated to the last import { createServerSideHelpers } from '@trpc/react-query/server' import superjson from 'superjson' import { appRouter } from '@railwai/api' import { createTRPCContext } from '@railwai/api' import { type CreateNextContextOptions } from '@trpc/server/adapters/next' const ssr = createServerSideHelpers({ router: appRouter, ctx: {}, transformer: superjson, }); export default ssr but I have typescript error : Type '{}' is missing the following properties from type '{ site: any; cookies: any; req: NextApiRequest; res: NextApiResponse; }': site, cookies, req, res because I have data in context, how I can get it ?

This is the explanation that I was looking for. 🙏🏻You are a gem. 🙌🏻Subscribed! 😁

Thanks for making this video, it's super helpful! I did some tests locally, with createServerSideHelpers, it indeed prefetched the data on the client. However, after checking the network requests, I noticed that there's still a request sent to the trpc api route on the backend after the page is loaded on the client, is this expected? Thanks!

thank you for this video, it has given more a lot more confidence in contributing!

This may have been one of the most helpful YT videos I've ever seens. Thanks!

Hi, great video! Time to share on my social (i barely got followers, but anyways, this is one of the rare videos about open source that I actually liked)

Hey would love your advice on finding growing orgs/repos. Are they more in web dev space or in more niche fields like web3 etc ?

really nice advice overall! I'm still stuck at the stage where I can't go beyond small bug fixes and improvements across many open source repos.. I want to dive deep and hopefully even work full time at a open source startup.

You answered most of my questions in this vid. I've been so terrified of contributing to open source projects. I don't know if i'm just afraid of judgement or if its the fear of breaking something, but I've never made the leap into it.. This vid sort of bolsters my confidence. Thanks!

/lgtm /approve

Great video dude 👏 You should make a video about ways to find this or that bug for make “improvements” in the repo or PRs

RUclips recomennded me this video. Some tips from me. The goal of OSS is not to become a maintainer of some project. If that's your only goal, you should check up on your complexes. Contribute with the mentally of "i want to help" not the "i contributed to big OSS and i want to boast that my PR got accepted". Find projects that interest you and you think it's worth to spend some of your time to push them toward their goal.