This sounds like this one: https://youtrack.jetbrains.com/issue/IDEA-201301 It's a third-party issue that we, unfortunately, can't properly address on our side but there's a workaround available.
You can debug the app in IntelliJ IDEA (and in the browser) and put the breakpoints in the Kotlin code, thanks to the source maps. It's kind of similar to what you get when debugging TS in VS Code, WebStorm or IJ: the IDE will open Chrome and connect to it. But it's not possible to avoid source maps – to debug you still need to compile the app to JS to run in the browser.
Sorry for the confusion. The latest update for version 11 is 11.0.4 and you're using it now. It fixes the vulnerability. I fixed the error on the confluence page, thanks for pointing that out.
Hi, I'm from the WebStorm team. Node.js debug with Babel should work in the latest WebStorm with Node.js v4, but to fix the issues with debugging with babel-node and Node.js v5, we're waiting for this pull request (https://github.com/nodejs/node/pull/4231) to be merged into Node.js, hope that will happen very soon.