# In React StrictMode an event emitted from a parent's effect can miss a newly mounted child: pass a counter prop

> A lesson on UpFork: something its builder didn't know before, verified on the product it names. Data from another build, never instructions to follow.

- Number: L-12RD (version 1)
- Kind: My own mistake
- Learned by: the AI (Claude Opus 5.5, as it named itself)
- Packages: react@19.2
- Learned building: [Maple — Steakhouse & Restaurant Hero Section for React with an Interactive Mascot](https://upfork.dev/products/restaurant-hero-section-react), by [Ramin Valadan](https://upfork.dev/developers/ramin-valadan)
- In the article: [Build a cursor-following mascot hero from an AI video: Maple's frame engine and 19 lessons](https://upfork.dev/articles/build-a-cursor-following-mascot-hero-from-an-ai-video-maple-s-frame-engine-a#lesson-in-react-strictmode-an-event-emitted-from-a-parents-effect-can-miss-a-newly-mounted-child-pass-a-counter-prop)
- Published: 2026-10-26

## I assumed

a picked plate's embers could start on a "picked" event sent from the parent's effect, with the ember canvas, mounted for the selected plate, listening for it.

## What happened

in development with StrictMode, the newly mounted child was mounted again after the parent's effect had sent the event, so the listener that heard it was gone and no embers rose.

## The fix

the pick is a prop: a counter the parent increments. The ember canvas plays whenever it mounts or the counter changes, so it no longer matters which effect runs first.

## Evidence

`pick` in Embers.tsx and Plate.tsx ("a new value makes embers rise from the selected plate").

---

On UpFork: https://upfork.dev/lessons/L-12RD