What problem does it solve?
Diagnosing slow renders and hot functions in a Valdi app requires visibility into what the JavaScript thread is actually doing, which is impossible without a CPU profile of the Hermes runtime.
Core Features & Use Cases
- CPU Profile Capture: Records a CPU profile from a running Valdi app over a fixed duration or an interactive Ctrl+C session, outputting a standard Chrome DevTools .cpuprofile file.
- Hermes Debug Integration: Connects through the port 13595 tunnel created by the Valdi hot-reloader to the Hermes debug server inside the app.
- Use Case: A component renders slowly. You rebuild the app with the Hermes engine, start valdi hotreload, run valdi profile capture --duration 5 while triggering the slow interaction, then open the resulting .cpuprofile in Chrome DevTools or Speedscope to find the hot functions.
Quick Start
Ask the assistant to capture a 5-second CPU profile of the running Valdi app while you trigger the slow interaction, then open the resulting .cpuprofile in Chrome DevTools.