DeepFrontend
Learning Paths
Practice
System Design & DS
Design Studio
Data Structures Curriculum
Real-World Case Studies
Careers
Job Board
Resume Builder
Blog
Sign in
Search
⌘K
Go Pro
Loading compiler resources...
Frontend Performance Quiz Practice
Active Recall Drill Session
← Exit Session
Question 1 of 1
hard
Frontend Performance
A code review finds useEffectEvent used to wrap an ENTIRE effect body, with the surrounding useEffect having an empty dependency array despite the effect's timing genuinely needing to restart on a specific prop change. What's the issue?
A
No issue — useEffectEvent eliminates all need for dependency arrays
B
useEffectEvent only extracts non-reactive value-READING — it doesn't eliminate the need for genuinely reactive dependencies; if the effect's OWN scheduling should restart on a prop change, that prop still belongs in the useEffect's dependency array
C
This is only a problem if the prop is a string type
D
useEffectEvent cannot be used inside useEffect at all
Check Answer