Share this article
Why I Stopped Using useEffect for Data Fetching
Every time I wrote useEffect with a fetch inside, something broke. Race conditions, stale closures, double-firing in dev mode. There's a better pattern — and once you see it, you can't write the old way again.
vivekkumarsingh.in/blog/stop-using-useeffect-for-data-fetching
Copy link
https://vivekkumarsingh.in/blog/stop-using-useeffect-for-data-fetching
Share on social media
Cross-post to blogging platforms
Clicking any platform copies the canonical URL to your clipboard and opens the editor. Paste it as the article's canonical URL to keep all SEO signals on this domain.
More on this subject: Modern Web Development.
ReactI read the docs three times. Watched two conference talks. Still confused. Then I grabbed a whiteboard and drew the request lifecycle myself — and suddenly the whole thing snapped into place. Here's that diagram.
8 min read
ReactI added useCallback everywhere because I thought that's what good React devs do. Then the profiler showed me my callbacks themselves were the bottleneck. Memoization has a cost. Here's when it's worth paying.
5 min readReactMost internal component libraries are created with good intentions and abandoned in six months. I've seen it twice. Here's what we did differently the third time — and the one decision that changed adoption.
9 min read