Console.log is not a valid way to display a message in HTML/javascript.
If you just open the Web browser's devtools you should still see a console with those messages?
The other bug I have no clue. Helpful suggestions are welcome.
The websocket disconnect one about server masking? And it doesn't happen immediately?
When the parse error occurs, please could you dump JSON.stringify(event.data) so we can see what's in it? I imagine that for some reason the data getting sent to the server is getting corrupted.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
If you just open the Web browser's devtools you should still see a console with those messages?
The websocket disconnect one about server masking? And it doesn't happen immediately?
When the parse error occurs, please could you dump
JSON.stringify(event.data)
so we can see what's in it? I imagine that for some reason the data getting sent to the server is getting corrupted.