Description: Investigate FMS's behavior under React 18 strict mode (development-mode double-invocation) and concurrent rendering features. Specifically: does useMotion survive a strict-mode double-invoke without producing duplicate animations or leaks? Are presence components safe under interrupted/replayed renders? Audit by enabling strict mode in a test harness and running representative motions. Land small fixes (e.g., guarding a side effect that should run once); defer larger architectural changes.
Why it matters: React 19 and concurrent rendering features are now widely deployed in product code. FMS components that fail under strict mode produce subtle bugs in dev that surface as flakiness in prod. This is an emerging-but-real concern — better audited proactively than after a bug report.
- Difficulty: Medium
- Sequencing: M3 W11
- Tags:
partner-pickup
Description: Investigate FMS's behavior under React 18 strict mode (development-mode double-invocation) and concurrent rendering features. Specifically: does
useMotionsurvive a strict-mode double-invoke without producing duplicate animations or leaks? Are presence components safe under interrupted/replayed renders? Audit by enabling strict mode in a test harness and running representative motions. Land small fixes (e.g., guarding a side effect that should run once); defer larger architectural changes.Why it matters: React 19 and concurrent rendering features are now widely deployed in product code. FMS components that fail under strict mode produce subtle bugs in dev that surface as flakiness in prod. This is an emerging-but-real concern — better audited proactively than after a bug report.
partner-pickup