IntelliJ and debugging Javascript issues

[Benjamin Tillman]

Hello everyone,

I've just installed a fresh copy of IntelliJ (14.1) and wanted to test Super Dev Mode out (GWT 2.7.0). Everything seems to be working fine except that any breakpoints I set in IntelliJ are not working. I'm really not sure what information is going to help solve this issue, so let me list some things basics I have done/tried:

- I do have the Jetbrains Chrome plugin installed and it connects to IntelliJ fine

- IntelliJ says it's connected to the Chrome extension

- I can use Chrome's developer tools to set a breakpoint within Chrome and this is respected just fine

- I've tried using Chrome 43 and and Chrome Beta 44

- I've followed https://www.youtube.com/watch?v=pdh2aKW2JPU (apart from setting up Tomcat on my local machine), including setting a breakpoint on the same line in the code as was done in the video, yet nothing.

I'm happy to work through this, but I'm not even sure where to start looking. Any help would be much appreciated.

Regards,

Ben.

[Jens]

Hm just tried it myself (using GWT 2.8 SNAPSHOT, IntelliJ 14.1.3) and I have to say that it seems to be broken.

I can only see the log output of chrome console in IntelliJ but break points do not work. I guess they do not work because IntelliJ does not see the SourceMaps provided by the SDM CodeServer. So IntelliJ does not know how to map your break point on a Java line of code to the corresponding JavaScript break point in Chrome debugger.

Normally when you run the JavaScript debug run configuration in IntelliJ you can switch to the "Scripts" tab in IntelliJs debug console and when you open the node for the SDM CodeServer you can browse the data found on http://localhost:9876/sourcemaps/app/ . However that is currently missing so IntelliJ does not see source maps.

I know that it does work in general because I already used it quite a bit some time ago. I guess either a Chrome or IntelliJ update has introduced a regression.

-- J.

[Benjamin Tillman]

I guess it was just bad timing on my part to start playing with this yesterday as opposed to me doing something wrong. See this IntelliJ issue which will be fixed next release.

Regards,

Ben.