lynx-debug-info-remapping
Debug Info Remapping
Description
In Lynx, main thread script is encoded to bytecode and uses an external debugging information scheme. Under this scheme, the row and column numbers in the runtime error messages are not the actual row and column numbers. The row and column numbers need to be deciphered from the external debug-info.json file.
debug-info.json format is as follows:
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.
889reactlynx-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.
54lynx-trace-record
This guide provides step-by-step instructions for recording Lynx performance traces. Use this guide when the user asks how to record a trace.
53