fix(diag): forward wasm panics to console.error with a readable trace (MAPPS-299) #284
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
psa-systems/mokosh-apps!284
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/MAPPS-299-wasm-panic-hook"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Installs
console_error_panic_hookas the very first call inmain()(beforesnapshot_initial_searchand the Dioxus launch) so the next reproduction of the "Schedule Appointment" wasm crash surfaces a readable panic message + stack trace in the browser console instead of an opaqueRuntimeError: unreachableat a hex offset (the QA repro reportedwasm:0x352c4f). This does not yet fix the underlying crash in the appointment form modal: it is the third acceptance-criterion item on the ticket and a prerequisite for diagnosing the first two. The hook is web-only (the desktop/native builds inherit the default Rust panic handler that already writes to stderr). Bundle impact is a couple of KB.#MAPPS-299