Exception cause in browser console

[faveoled]

The code throws an exception with a cause:

        RuntimeException inner = new RuntimeException("Inner");
        throw new RuntimeException("Outer", inner);

I have the following in my browser console:

Is there a way to also have "Inner" exception message in the browser console? I expected it to appear similar to regular Java exceptions.
JRE sample output:

Exception in thread "main" java.lang.RuntimeException: Outer
	at MyClass.main(MyClass.java:4)
Caused by: java.lang.RuntimeException: Inner
	at MyClass.main(MyClass.java:3)

[gkdn]

We populate the cause property of the JS errors.

This is relatively recently standardized so DevTools might not have caught up with them yet. You can file a bug with Chrome or the browser that you are developing with.

Being said that if you pause, then you can still inspect the error object and inspect/print the cause field of it.

[faveoled]

this is not the upstream version and bugs should be filed against our fork

Thank you, I wasn't aware of that

[gkdn]

Actually we started populating this property quite a while back but further iterations of Throwable enabled potential name mangling of cause on the JS Error object.

After this is standardized and JsCompiler added cause to the externs (around June 2022) this should be all working as expected for JS debugging of the optimized builds.

[niloc132]

Thanks for the added suggestion of closure-compiler - in the commit where j2cl-maven-plugin updated to 0.11.0, it also was updated to the nov 2022 release of closure compiler, see Vertispan/j2clmavenplugin@b4159cd#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8

Assuming you are using j2cl-maven-plugin 0.21-SNAPSHOT, you likely have the dependencies required for this, or are you running with our maven release in some other way such that an out of date closure might be in use? If you are running in the j2cl-maven-plugin and still seeing this issue, I'd feel better if you filed a ticket with us rather than here, to make sure we rule out our own forks having caused any of this.

[faveoled]

I had j2cl-maven-plugin 0.20, J2CL version was configured via a property which likely wasn't even picked up. Maybe I'll try 0.21 when it's released

[niloc132]

Yes, that will have an older closure-compiler too. Perhaps try the snapshot build, we're looking to release it soon.