2 Replies Latest reply on Apr 25, 2017 10:17 AM by mbarkley

Tips for debugging minified JS

mjm.ent Apr 7, 2017 12:32 PM

Hi,

The JS console output is completely unreadable and impossible to locate the source of problems, very frustrating considering the long compile time for GWT.

Are there any compiler options which allow for original varible names to be adapted in the generated JS ?

Any other tips ?

1. Re: Tips for debugging minified JS

saso5 Apr 9, 2017 8:11 AM (in response to mjm.ent)

Upgrading to RC2 did make the stacktrace more readable for me but I still need to invest some time to figure out where the error is.

Errai Developer Blog: Errai 4.0.0.CR2 released!
Actions
2. Re: Tips for debugging minified JS

mbarkley Apr 25, 2017 10:17 AM (in response to mjm.ent)

There were fixes in 4.0.0.CR2 that improved stack traces in logging so that the source line numbers are displayed in the Google Chrome dev console.

In my experience, using debugging in Google Chrome with source maps has been fairly straightforward, if a little less convenient than debugging plain Java. For the rare times that doesn't work, I will compile with "-style PRETTY" so that the compiled JavaScript is human readable.
Actions

Go to original post