How many times have you silenced the ESLint warning just to make a useEffect work… and then somehow ended up in an infinite re-render loop? In this video, I break down the new React 19.2 hook, useEffectEvent, and why it finally fixes the most common useEffect pain: stale closures, dependency array chaos, and effects re-running for reasons that have nothing to do with the actual side-effect. I walk you through a real chat app example where toggling dark/light mode keeps reconnecting the chat. The connection should not restart just because the theme changed—but because theme is referenced inside the effect (for a toast), it gets forced into the dependency array, and now the effect re-runs. With useEffectEvent, I extract that “non-reactive” logic (like reading the latest theme for a toast) into an Effect Event, so the effect stays stable and only re-connects when it actually should (like when roomId changes). My takeaway: treat Effect Events like event handlers you trigger from effects. Use them to break the chain between “this effect must re-run” and “this callback needs fresh state.” And don’t use it as a band-aid—if the logic doesn’t belong in an effect, fix the logic instead of wrapping everything just to silence ESLint.