A guide to using Next 14 (server actions, RSC, useFormState, useFormStatus)

[pablus-rh]

Cody, your teaching style is truly exceptional and best of all: no unnecessary fluff. I just immersed myself in a series of your videos and gained so much valuable knowledge.
Thank you very much, and thanks YT for putting your channel on my feed! 👍

[codinginflow]

You can also skip noStore if you revalidate the path from your server action. That's incremental static regeneration.

[franinja]

This is great, I always get overwhelmed when there is too many features being added to something I use, love seeing these videos just running over the changes

[oussamachahidi]

Thanks man, you're always on time i really needed that ! plus your explanation is easy !

[isaackoz]

Fantastic video thank you! I think I'm gonna make the switch from tRPC to server actions finally

[focusotter]

Saw you repost this video on Twitter, glad I bookmarked it and came back to watch it. Great stuff!

[herozero]

Thanks man! I think todo app is perfect if the focus is learning these kind of features.

[harunalrd]

Just searching for drizzle and your vids showing up - uploaded 2 min ago 😂

[haydenthai]

Cody youre the🐐This video was super helpful!

[anonymousnoob]

Excellent Video! Keep up the good work!

[antonbyrna]

For checkboxes you could probably still use input with a button then make this button to be transparent and position it on top of a checkbox

[nettion]

I finally understand server actions now lol thanks dude

[sorknerl]

Would people still recommend using tRPC with Next14? Loving the videos Cody!

[ktrifon]

Excellent! How about using a server action to do a search based on criteria of a form, and display the returned data back to the screen? Everyone on youtube shows examples like yours (inserts or deletes) and then they display ALL the data. But I would like to see an action to do simple query (using conditions from the form).
In this case I am not sure what to do. The component containing the form will still be a server component like in this example? The results, if they are displayed in a separate component, a results component, then that results component will also be a server component? (I guess that in this case the app will look like a php app, totally) or a client component? Am I thinking to the right direction or the approach should be different? Should I return to the fetch/API/useState approach?
Thanks man...

[reqtified]

Hey Cody, I built an app that was on the page router last year, a nice s ide project that makes abit of money with the OG page router t3 stack. Im now working on my 2nd side project, and might learn app router and drizzle orm (instead of prisma) can I ask why tRPC can still be an option even in the app router on T3? Is it only used for client side calls or is it both? Really confused but would love to know.

[EdygarOliveira]

Instead of encapsulating the create form into its own component, you could’ve just gave it a key unique, couldn’t you? Maybe based on the length of the todos or some fingerprinting of the set

[ibex]

Can you please resume the react interview series, they were really fun to watch

[zhenobiikuzo]

hii, may I ask why we still need react hook form in server actions?

[noelrohi]

Noticed that drizzle has an icon in your vscode icons, what icon extension are you using?

[srah_k]

For someone building a new production app, would you recommend prisma or drizzle now that you have played around with them both? Would love your input on this