Post

If you are totally against setting state in a useEffect, how would you recommend doing this kind of thing? Assume a SPA.

nox — oss/acc

@wriddhi.com

1 Dec 2024

Honestly just use @tanstack.com react-query's useQuery, it's so much cleaner for client side fetching. Or there's always the async RSC route.

Jack Herrington

@jherr.dev

For sure. I'm just seeing folks saying "setting state in any way in a useEffect is bad", and I'm curious as to 1) why, and/or 2) where that information is coming from.

1/12/24, 5:42 pm0 reposts6 likes

nox — oss/acc

@wriddhi.com

1 Dec 2024

I think that is more paranoia from seeing bad code inside useEffect that tanks performance like 2 useEffects updating states that are in each other's dependency array or using useEffect to set a new state that should be a simple derived variable with maybe a useMemo.