Displays traceback/js errors in the browser

[berinhard]

Currently people have to keep an eye in their browser's console for both js errors (if using transcrypt) and python errors (if using pyodide).

The ideal scenario would be to have some type of HTML element displaying all error messages that pop up in the browser's console.

[villares]

Hey @macarena, I bet you could add this single-handedly and with your eyes closed...

[Vamoss]

[PT]
Uma abordagem a ser considerado é interceptar a função javascript e injetar codigo nela.
https://stackoverflow.com/questions/9216441/intercept-calls-to-console-log-in-chrome

Em um projeto que vi interceptando o log, observei uma perda de performance considerável. Então já recomendo uma maneira de renderização desses logs no HTML da forma mais simples possível, sem parser ou tratamentos que sejam custosos ;)

[EN]
One approach to be considered is to intercept the javascript function and inject code into it.
https://stackoverflow.com/questions/9216441/intercept-calls-to-console-log-in-chrome

In a project that I saw intercepting the log, I noticed a considerable loss of performance. So I already recommend a way of rendering these logs in HTML in the simplest possible way, without parser or treatments that are costly;)

[msawired]

Shining some light on this topic from OpenProcessing wisdom: Vamoss is correct that any interception and adding HTML elements to display errors and logs causes some performance drop, but it has its benefits as well. ie. user-friendliness etc. That's why I made it a user-preference option to toggle html console on/off.
Console overrides for console.log, console.warn, console.error... works pretty well. Catching and printing errors however is challenging, as some error events may have sandboxed elements that can not be passed outside the native browser console. For that, and as a general helper, I use stacktrace.js to extract the minimal necessary information, and show it to user on html console. I'd be happy to look into it when I start adding python to beta version on OP.

[berinhard]

I have a feeling that #189 will be a facilitator to this task. The idea to expose a JS entry point as a Promise, will enable the client code to handle the errors raised from the promise. I'm just leaving this note here as a personal reminder =)

[berinhard]

This should also be added to the demo editor