prigara

4 ms·

1. 1.▲
   by prigara 5y ago

   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.
2. 2.▲
   by prigara 9y ago

   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 Chr
3. 3.▲
   by prigara 10y ago

   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.
4. 4.▲
   by prigara 11y ago

   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:/&#
5. 5.▲
   Spy-js: JavaScript tracing tool(blog.jetbrains.com)

   2 points by prigara 12y ago|0 comments