This Is The Way.. Next.js Server Actions with next-safe-action & Sentry

[@DaveGrayTeachesCode]

Use the code "davegray" for 3 months free on the Team plan of Sentry for any new accounts: bit.ly/try-sentry-dg

[@oladapooluwadurotimi2865]

Well done sir. Nice course ❤.

[@DaveGrayTeachesCode]

Thank you!

[@Quinn55455]

Great job explaining Dave, thanks again for another good tutorial!

[@DaveGrayTeachesCode]

Glad you enjoyed it!

[@SkyrimBeast]

3rd to comment. Thanks Dave, your video's have been an invaluable resource 🙂

[@DaveGrayTeachesCode]

I appreciate that! 🙏

[@Elizabeth-h8l5x]

Great content, as always! I need some advice: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?

[@YabseCoder]

Great job , Professor we gonna hit 1M in 2025 hopefully sir ❤

[@vispz]

Thank you, Sir. I owe the knowledge I have to you. I hope that one day I can support you in return ❤.

[@DaveGrayTeachesCode]

Glad I have helped!

[@vispz]

@@DaveGrayTeachesCode ❤

[@MyGeorge1964]

Nice course, thank you. Have you thought of adding a multi-language component to this project?! Just asking...

[@DaveGrayTeachesCode]

Good suggestion! It won't be part of the core series, but I have several features that I plan to do short add-on series for this after the main series is finished.

[@MyGeorge1964]

@@DaveGrayTeachesCode Great! Many thanks.

[@ilan117]

Hi Dave, I am not very sure that’s the best error handling. I never used next-safe-action before but with the tools I am usually using I could prompt the user on a form that an entry e.g. a phone or an email is already existing. Now having this done your way, if for example you try to create a customer with existing email or phone the user is prompt with the following message “Database Error: Your data did not save. Support will be notified“, I am doing something wrong?

[@DaveGrayTeachesCode]

@@ilan117 No you're not doing anything wrong. You can absolutely look for specific errors and give tailored messages to the user if you want to. You could even be more proactive and provide that information immediately like GitHub does when you create the name of a repository. At some point I have to stop with features or the tutorial would go on forever. Please make it your own as you go. That said, I may add your request in before the series ends. I can see how it is desirable. 🙌

[@LeonegasHolmes]

Hi Dave. Thanks for making such well explained videos with up to date concepts. Learn a lot with them. But i have a question. With the new react hook “useActionState” with zod and custom validation, does it still make sense use a library like next safe actions? I know it requires a little more code to make it work but it makes you less dependent on future changes on a external library i think. Thank you again!

[@DaveGrayTeachesCode]

There is always that consideration with any external library. You can create everything from scratch, but libraries help. I currently like and use the patterns established with next-safe-action, but you can forego it if you (or your dev team) decides to.

[@celsopires1999]

Hi Dave, When we try to insert a customer with an existing email address in the database, we get an error. Could you please advise on the best approach for detecting this issue and sending the error message to the client side? Thank you!

[@DaveGrayTeachesCode]

@@celsopires1999 yes, I'll be adding that in the next video I publish (chapter 12).. final changes before deployment.

[@mrbilchalan]

I thought you will use useActionState instead of next-safe-action. The two hook almost same what I understand still now. Then why we use next-safe-action? Hey, I am still new in this tech and mess up with myself often. Thank you again.

[@DaveGrayTeachesCode]

I think you will see and understand why I chose next-safe-action as you complete the video. I explain why I like it throughout.

[@craigmcclanahan8410]

Hi Dave, I am really enjoying the content you are presenting in this series. But I ran into a question about what to do if your database table has constraints like "unique" or "foreign key". The Zod schema won't catch this kind of thing. In many of my older apps, I've gotten around this by using async processing in Zod to do the checks as the form is being filled out. In the case here, in the Customers table for example, the uniqueness checks on email and phone will trigger database errors on an INSERT or UPDATE if they are violated. That in turn will cause a relatively meaningless error returned to the user, without any indication of what the actual problem is. It would be a good idea to at least catch these constraint violations to give the user an idea of what they have to fix.

[@DaveGrayTeachesCode]

That unique duplicate entry error is handled in the video that just published today. Drizzle schemas do support foreign key relations. It just depends on the type of database you're working with.

[@craigmcclanahan8410]

@@DaveGrayTeachesCode Awesome! Looking forward to it.

[@AldisSv]

Hello. First of all, thank You for this awesome series. I wonder, why some fields like those optional ones, have .trim(), but others dont? Shouldn't we .trim() all fields? Also, is it really possible to send data to that saveCustommerAction from another source rather than our form? Do we really need validation inside that serverAction if we dont have backend API endpoint which triggers that function?

[@DaveGrayTeachesCode]

@@AldisSv yes, you can trim all fields if you want. I only focused on the optional fields in preference of null over an empty string when the field is not required.

[@craigmcclanahan8410]

In regards to needing server side validation, you absolutely need to do that. A server action is implemented with a POST call to an endpoint created by the action, without you having to build it. However, this endpoint does NOT have any validations of its own! You will need to check authentication and run schema validations on the server side, just in case someone nefarious has reverse engineered how to call that endpoint (it's not hard to do this) themselves.

[@AldisSv]

@@craigmcclanahan8410 Thank You for clarification. Now I get it, server actions generate API endpoints without us explicitly defining them with api folder structure route.js files.

[@mrbilchalan]

I don't know if you have enough time, Please consider a tutorial for next-auth. I know you have a tutorial about it, but that is not enough for people like me. There are many things like strategy, access token, refresh token, rotation between them and others are not cleared. Thank you.

[@hamudxd9497]

HELLO SIR PLEASE LAUNCH A COURSE OF NEXT FOR ABSOLUTE BEGINNERS FFOM BASIC TO ADVANCED

[@BryanOnyeji]

Really nice course. Sir I've been following all your courses especially your HTML CSS and JavaScript course I've been a devoted fan of your work but recently my laptop just got spoilt and now trying to find new ways to code please if you can assist really appreciate you thank you. Thank you for all the free courses, you've really impacted a lot of teens in Nigeria.

[@DaveGrayTeachesCode]

Glad I've helped you. I'll continue to offer free content but I don't send out laptops.