Workflow with webpack's eval-source-map in Firefox

[smg...@gmx.net]

Take this expected error for example:
----------------------------------------------
TypeError: gl is undefined[Learn More]
app.bundle.js%20line%201350%20%3E%20eval:397:7
----------------------------------------------

Clicking that link opens a new tab with errors => useless.

So I was wondering whether maybe that type of source map is not suitable for debugging. Until I tried the same thing in Chrome:

----------------------------------------------
Uncaught TypeError: Cannot read property 'VERTEX_SHADER' of undefined Renderer.js?be4e:484
----------------------------------------------

Errors in the same spot but the link correctly points to webpack:///

Then I realized... oh hang on a second - if I expand the error in Firefox, I get a webpack link to the correct line in the code too!
But... that's of course a subpar workflow, having to expand errors to get to the source map link.

Hence my question: Does Firefox have some setting somewhere that causes that eval link to be replaced with a webpack one?

[Armen Zambrano Gasparnian]

I filed this issue in here:
https://github.com/devtools-html/debugger.html/issues/7445