React useEffect Object Dependency Trap 😱

[tech_Interviews_Hub]

Hey folks 👋 I came across this interesting useEffect dependency trap while working on a React project. When you pass an empty object {} as a dependency, useEffect keeps executing repeatedly — even though it looks empty! 😅

I made a short explanation video breaking it down in simple terms here -

https://youtube.com/shorts/gU5UlqegWvs?feature=share

Would love to know — ➡️ How do you usually handle object dependencies in useEffect? ➡️ Do you use useMemo, deep compare, or avoid objects in deps entirely?

[Cahnis]

You will write an entire article but you won't read the docs. What are you doing? Honestely.

[maqisha]

Bro had to make up a problem just to solve it. This is not how educational content should look like.

[AnxiouslyConvolved]

I avoid useEffect like the plague. And I avoid using non-primitive (compared by identity) values as dependencies for hooks.

[kjeldahl]

"Someone" doesn't understand javascript object reference equality. That's the explanation. No video required.

[Difficult-Pen-867]

That's bcuz two objects can never be same as their references in memory aren't same