You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently panics are printed to the dev console. However, the errors are not manifesting in the web UI. It is not a great user experience.
I understand that the goal of the crate is to print to console, however I am looking for ways to pass the panic info from panic hook into my web application. I run a WebAssembly module in a WebWorker. What are my options?
Is there a way to emit a DOM event from the panic handler somehow and use e.g. AddEventListener() to subscribe to it?
What are the options for a WebAssembly module running in a WebWorker? (it does not have window and some of the other functionality compared to the main thread).
I am using React for UI, Recoil for state handling, and Observable for events.
Any thoughts or ideas?
Proposed Solution
I am looking for possible solutions yet.
Alternatives
I am looking for possible alternatives yet.
Additional Context
N/A
The text was updated successfully, but these errors were encountered:
Motivation
Currently panics are printed to the dev console. However, the errors are not manifesting in the web UI. It is not a great user experience.
I understand that the goal of the crate is to print to console, however I am looking for ways to pass the panic info from panic hook into my web application. I run a WebAssembly module in a WebWorker. What are my options?
Is there a way to emit a DOM event from the panic handler somehow and use e.g.
AddEventListener()
to subscribe to it?What are the options for a WebAssembly module running in a WebWorker? (it does not have
window
and some of the other functionality compared to the main thread).I am using React for UI, Recoil for state handling, and Observable for events.
Any thoughts or ideas?
Proposed Solution
I am looking for possible solutions yet.
Alternatives
I am looking for possible alternatives yet.
Additional Context
N/A
The text was updated successfully, but these errors were encountered: