When is `useEffectEvent` appropriate, and when should a value remain an Effect dependency?

Separates reactive synchronization inputs from non-reactive logic that still needs the latest props or state.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A value stays in the dependency list when changing it means the external synchronization must rerun. I use useEffectEvent for logic called from an Effect that should read the latest props or state without making the Effect resubscribe. For example, changing a room ID reconnects a chat, while changing the current theme only changes the notification shown after connection.

Full answer below

Practice focus

React 19 Effect Events, dependency reasoning, stale closures, reconnection behavior, and misuse boundaries.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Effect Events solve a narrow stale-closure problem; they are not a general escape hatch from reactive dependencies.
A value stays in the dependency list when changing it means the external synchronization must rerun. I use useEffectEvent for logic called from an Effect that should read the latest props or state without making the Effect resubscribe. For example, changing a room ID reconnects a chat, while changing the current theme only changes the notification shown after connection.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I first describe the Effect's lifecycle in plain language. Its dependencies are the values that define that lifecycle, such as a URL, room, or subscription key. Notification text, analytics context, or another non-reactive read can move into an Effect Event if it must be current when invoked. I do not use it to hide a missing dependency, pass it to children, or call it outside Effects. The lint rules are useful evidence, not an obstacle to suppress.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using an Effect Event to silence every dependency warning.
Removing a value that defines the subscription identity.
Calling an Effect Event from user events or child components.

When is `useEffectEvent` appropriate, and when should a value remain an Effect dependency?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Prerequisite

Tech stacks

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?