lynx-trace-record
1. Workflow Example
The recording process requires using the trace_record CLI tool. The order of operations is critical.
Step 1. List connected clients:
First, list all connected clients to get the client ID. This helps you identify which app to trace.
- If you have multiple connected clients, ask the user to specify the client ID you want to trace. Then, use this ID with the
--clientparameter to trace. - If you have only one connected client, you can omit the
--clientparameter. - If no clients are found, prompt the user to connect their device via USB and open the debugging app.
node <path_to_the_skill>/scripts/trace_record.bundle.cjs list-clients
Step 2. Start recording:
Execute the start command BEFORE building or opening the page on your device. This ensures you capture the entire first frame of the page. Use the --client parameter with the client ID from Step 1.
node <path_to_the_skill>/scripts/trace_record.bundle.cjs start --client <client-id>
More from lynx-community/skills
lynx-devtool
Interact with Lynx DevTool to inspect and debug Lynx applications. Use this skill to list connected clients and sessions, send Chrome DevTools Protocol (CDP) commands, send App commands, and open URLs in Lynx. This is useful for debugging UI issues, inspecting runtime state, or automating interactions with Lynx apps.
854reactlynx-best-practices
ReactLynx best practices covering dual-thread architecture and React patterns. Provides rules reference for writing, static analysis for reviewing, and auto-fix for refactoring.
70lynx-typescript
|
67lynx-trace-analysis
|
55debug-info-remapping
Remap the function_id:pc_index to the original source code position by provided debug info json file.
54habitat-usage
Guidance on using Habitat to manage multi-repo source and asset dependencies via .habitat/DEPS and hab sync, plus troubleshooting common sync failures.
41