Moving over to proper debuggable configs

[Garethp]

Test Before Merging

This is a big change, try it before you merge

What it does

• Let's you debug the Typescript without the TsDebug Action
• Doesn't create a node RunConfig for the debug
• Gradle let's you test the plugin better

Using gradle is a big change. It will let you launch Webstorm with your plugin automatically. It also lets you put debug points in your plugin, so you don't have to use the log for info any more. Changing this line will let you specify what IDE to open it with

If you have questions, please ask

[bluelovers]

how to use?

[Garethp]

Updated. See below:

build:

output:

Run:
Change this line to the directory of your webstorm

Then click

[bluelovers]

with 2 by this pr, it start twice and debug point is not work

with 1 (old way)

[Garethp]

Only starts once for me. This is my build. Try it?
idea-run-typescript-2020.08.20.0.zip

[bluelovers]

hmm use ur build, i still get twice

---

and somehow, my build and ur build all failed on ansistyle in my webstorm 2020.2

but work on idea 2019.3.5, 2020.2.1 rc

---

hmm but also work on sandbox of webstorm

[bluelovers]

i think code is merge into current master now, if see any miss , tell me xd

[bluelovers]

also add hidden feature

when add nodejs.console.use.terminal into env var will overwrite ide registry

idea-run-typescript/src/io/plugin/tsnode/lib/cmd/NodeJSCommandLine.kt

Line 29 in 975b4b1

val v = runConfig.runSettings.envData.envs.get("nodejs.console.use.terminal")

[bluelovers]

@Garethp twice bug is from esm-ts-node