I've just started work on quite a big pre-existing project using Typescript and Webpack for the front end and Java for the backend, and I've been trying out IDEA to see if it offers better support than Eclipse.
IDEA certainly promises to work, and is tantalisingly close, except for the issue described bellow:
I have created a project, told it about my TypeScript source files etc, and configured a JS debug configuration which maps "webpack:///." to the root of the project. I actually run sbt to bring up the backend and launch the webpack-dev-server, but anyway, webpack starts and I launch the debug session in IDEA.
IDEA opens a page in Chrome and connects the debugger to it as expected, and outputs to the console.
However, if I create a breakpoint and refresh the page, it doesn't work, i.e., Chrome doesn't stop at that line.
I would have thought I had set it up wrong, except for that fact that I can insert "debugger;" statements and it works as expected: when the code reaches the statement it stops and jumps to the correct line in IDEA's debugger, and the editor is annotated, I can inspect variables and step into methods which are defined in other files and everything. Also "console.log()" messages report the right file / line, which I can click in the IDEA JS console and it take me to the right source file in the project
So, I feel like source-maps must be working, and the debugger is connected. I'm just curious as to why it seems that IDEA cannot tell Chrome about it's breakpoints in this project.
I have also tried the angular2-seed project and that works 100% as expected: I can set breakpoints and Chrome stops where it's supposed to. So it's funny that it doesn't work in my project.