This article assumes that you’re somewhat familiar with useEffect API. It’s only after I stopped looking at the useEffect Hook through the prism of the familiar class lifecycle methods that everything came together for me. In fact, we’ll spend most of our time unlearning. The goal of this article isn’t to give you a list of bullet point recipes. To see the answers, we need to take a step back. This deep dive will make the answers to these questions look obvious to you. I’ve since had a few “aha” moments that I want to share with you. Even when writing the initial docs, I didn’t have a firm grasp on some of the subtleties. When I just started using Hooks, I was confused by all of those questions too.

🤔 Why do I sometimes get an old state or prop value inside my effect?.

🤔 Why do I sometimes get an infinite refetching loop?.

🤔 Do I need to specify functions as effect dependencies or not?.

🤔 How do I correctly fetch data inside useEffect? What is ?.

🤔 How do I replicate componentDidMount with useEffect?.It seems similar to class lifecycles… but is it really? You find yourself asking questions like:

You have a nagging feeling that you’re missing something. “Great job”, they said.īut sometimes when you useEffect, the pieces don’t quite fit together. You even made some custom Hooks to extract repetitive logic (300 lines gone!) and showed it off to your colleagues. You’re comfortable with the API and picked up a few tricks along the way.

Civ 5 cheats that dont resync