5 Hidden React Server Function TRAPS Beginners Fall Into

[@snsa_kscc]

This content is second to none, but man, the more I stick with react/next.js, the more I feel I'm in the world of pain and footgunning. Much love, Jack.

[@eljaz00]

The amount of info you give immense that I have to pause the video many time to make sense of this stuff

[@yzz9833]

You been posting some bangers lately Jack

[@armaandhanji2112]

Hi Jack. Love your content. Would love to see your take on Tanstack Start! (I've been loving it so far).

[@jherr]

Definitely planning on it. Please tell me what you like about it.

[@umavictor]

Thanks Jack. Your content is invaluable

[@frostmichael8360]

Awesome content, Thanks !

[@whynot9963]

Awesome video, as always. Quick question, how do you get the terminal to show that LSP style autocomplete for commanda you can run?

[@TheHoinoel]

nice video! I know you're advertising your course with it, but I would love to see how to cache server functions. I am totally confused as to when and what will be cached

[@couragic]

20:10 returning component from server action smells like htmx 😊

[@prashlovessamosa]

I was excited when server actions and other stuff were introduced now I am totally confused about the server function action wtf going on in the react ecosystem. I am all in for Svelte.

[@ivan.jeremic]

just use svelte why comment.

[@prashlovessamosa]

@@ivan.jeremic I have to learn react as no one pays me for writing Sveltekit as a lot of crackers still exsist you are one of them

[@MerthanMerter]

​@@ivan.jeremic because comments were invented to get feedback, thoughts and ideas from community? in fact why would you comment something like that?

[@panoscool_]

Hi Jack, can you share the github for these examples pls?

[@jherr]

Yeah, I'm on the road and away from the machine that had the final code. I'll post it tomorrow (wednesday) morning.

[@panoscool_]

@jherr thanks a lot!

[@avneet12284]

Is there a repo for this? Nice content

[@Fuzbo_]

Still don’t see the value prop for server functions specifically other than type-safe return types, co-locating data fetches / mutations, and ability to submit forms without JS. For every benefit they offer it feels like it comes with 10x as many gotchas or footguns.

[@yzz9833]

Personally, I would say a large value prop for server functions is actually being able to return entire components as html instead of rendering them on client. This also seems like a more graceful way of handling state changes in the dom versus doing it programmatically and risking re-renders.

[@LehmannMr]

Maybe you give next-safe-action a try. The code looks so much cleaner.

[@AlainDuchesneau]

That was pretty fast! 😵‍💫

[@LehmannMr]

Whoever wants to work with server actions should take a look at the next-safe-action package which includes things like validation. Also be aware that server actions are an api endpoint which can be accessed via http directly and always should be checked for authentication and authorisation.

[@aveshlutchman8573]

Server functions being unable to run in parallel is such a bummer. I have an app that uses a lot of Promise.all since i have many asynchronous tasks running. It sucks that i can't realistically use server functions for some tasks because of this. For example i have a transcript editor which has multiple segments, each segment having their own start and stop times. I would use server actions to load all of the data for each segment, but based on this info, i guess I'll have to use route handlers.

[@vitorfigueiredomarques2004]

You Just need to call Promise.all in another sever function.

[@Niksorus]

Next.js and React did a terrible job at implementing this pattern. Even MORE footguns in React ... In the meantime, all the other frameworks find more elegant solutions, like Astro server actions.

[@MerthanMerter]

J.H: god of react

[@mpiorowski]

This is like the perfect advertisement to not touch React, even with the longest stick. 😄

[@brianllllll]

Lol

[@cafelutsa_]

Don't touch it, no need for more mediocre React devs to join the soup of bad code

[@AdamK3l]

What do you recommend instead?

[@m12652]

@@AdamK3l SvelteKit

[@LehmannMr]

​@@m12652Hm. If you look at the numbers of react applications compared to svelte I don't think it is a good choice. Also if you look how many good react tutorials are out ther for react compared to svelte.

[@adambickford8720]

That concurrency model will cost the industry billions.

[@Tay74514]

React IS the trap 🕳️😂

[@macccu]

We are literally back to PHP returning parts of template from backend lol. Soon there will be tons of low quality React tutorials that will teach newcomers to mix backend and frontend code creating all famous "spaghetti code". Then will we will go "hmm there must be a way to split front and back!"

[@vitfirringur]

It's not the same, friend. You are just demonstrating your ignorance here. You're not returning a "template".

[@yzz9833]

@@vitfirringurthis

[@adambickford8720]

@@vitfirringur Might want to brush up on your history. This is a very, very old idea.

[@o_glethorpe]

The best not so hidden mistake is to actually put react on the server.