Normally, Chrome devtool can never figure out how useEffect is called
However, if we wrap the onClick inside a setTimeout, we can see onClick before effect in the callstack
How can this happen, what kind of magic setTimeout did on Chrome?
Normally, Chrome devtool can never figure out how useEffect is called
However, if we wrap the onClick inside a setTimeout, we can see onClick before effect in the callstack
How can this happen, what kind of magic setTimeout did on Chrome?