A place for developers to talk about building on Farcaster.

/dev

https://react.dev/learn/synchronizing-with-effects#how-to-handle-the-effect-firing-twice-in-development

React is hard because you need to write idempotent logic in a rendering loop lol

It’s time for me to stop fooling around and really optimize my React knowledge. It’s not enough anymore to “get the job done”, I really want to understand how things work.

Update: useEffect is a powerful tool so be careful when using it because it’s very easy to fuck up the performance of your app.

Generally, you should not use useEffect when fetching data in a client-side app (not like I did until recently). Instead, you should use your meta-frameworks’ data fetching API (e.g Remix does that very well) or use React Query.

Why? Because in dev mode, your custom useEffect will run twice and you’ll have to implement idempotent logic on top of the React useEffect boilerplate code.

+ caching + preventing network waterfall (fetching the data of all the children components not displayed)

Put that in a reusable logic and you got yourself a less-good ReactQuery and we’re back full circle.

I realized that recently and it feels weird to feel like everything you wrote before is shit lol.