Is there a way to make stacktraces work with sourc...

# javascript

[karelpeeters]

Is there a way to make stacktraces work with source maps? I do get the line the error was thrown on originally in symbol-version, but the stacktraces show the js line numbers.

[konsoletyper]

I don't know. For me this works. Can you provide additional information? Browser version, attach a small project that reproduces the issue? Did you try another browser?

[karelpeeters]

I'll try to create a small project that reproduces this.

[karelpeeters]

https://github.com/flaghacker/KotlinSourceMapBug

[karelpeeters]

Firefox doesn't even show line numbers or stack traces at all.

[konsoletyper]

Yes, I could reproduce the problem. However, there's a workaround: after I push F5 (keeping devtools open) the application re-runs, error get re-thrown and I can see proper stack trace.

[konsoletyper]

^ @karelpeeters

[konsoletyper]

Looks like it's a problem in Google Chrome. I could reproduce it with a plain JavaScript:

function MyError() {
    this.name = "MyError";
    this.message = "!!!";
    Error.captureStackTrace(this, MyError);
}
MyError.prototype = Object.create(Error.prototype);
function foo() {
    bar();
}
function bar() {
    throw new MyError("!!!");
}
foo();

[karelpeeters]

I see, I'll try that when I get the chance.

[karelpeeters]

Hmm, the F5 trick doesn't appear to work for me, although somethings definitely changing. Before:

https://i.imgur.com/Jvwr9M7.png▾

, after:

https://i.imgur.com/cJOtv1O.png▾

.

[karelpeeters]

Still only JS line numbers though.

[konsoletyper]

You press wrong button

[konsoletyper]

Did you see a small triangle to the left from "Uncaught" on the second picture?

[karelpeeters]

Ah, you're right, thanks!

[karelpeeters]

Is this something that should be reported to google?

[konsoletyper]

I guess, yes