What problem does it solve?
Trace every interactive touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.
Core Features & Use Cases
- Map state stores and their actions to understand how changes cascade.
- Trace each touchpoint (onClick, onSubmit, onChange) to identify sequential undo, race conditions, stale closures, and missing transitions.
- Generate actionable reports highlighting patterns like Sequential Undo, Async Race, and Stale Closure with recommended fixes.
- Use Case: Debug a complex form flow where a button action sets a flag but a subsequent handler resets it.
Quick Start
Trace every interactive touchpoint on the target area by mapping each handler, following the sequence of state-changing calls, and identify where later actions undo earlier changes.