Bugzilla

I'm writing a modern JS application with async/await and promises, and I expect to get stack traces when things go wrong. However, unlikely Chrome, Firefox does not yield any stack traces at all, just going "TypeError" and then leaving me to figure what code path got me to that type error, which basically means I cannot use Firefox for actually testing and debugging modern code.

And that seems... bad?

Attached screenshot shows the information "that something went wrong, and where" that Chrome yields, versus the information "that something went wrong" and then nothing by Firefox.

I'm writing a modern JS application with async/await and promises, and I expect to get stack traces when things go wrong. However, unlikely Chrome, Firefox does not yield any stack traces at all, just going "TypeError" and then leaving me to figure what code path got me to that type error, which basically means I cannot use Firefox for efficient testing and debugging modern code.

And that seems... bad?

Attached screenshot shows the information "that something went wrong, and where" that Chrome yields, versus the information "that something went wrong" and then nothing by Firefox.

I'm writing a modern JS application with async/await and promises, and I expect to get stack traces when things go wrong. However, unlikely Chrome, Firefox does not yield any stack traces at all, just going "TypeError" and then leaving me to figure what code path got me to that type error, which basically means I cannot use Firefox for efficient testing and debugging modern code.

And that seems... bad?

Attached screenshot shows the information "that something went wrong, and by which code path" that Chrome yields, versus the information "that something went wrong" and then nothing else by Firefox.