@robert So after a bit of debugging I found out that the executed task when having default launch for krom is :
> Executing task: /home/jsnadeau/Documents/KodeStudio/kodestudio --khamake /home/jsnadeau/Documents/projects/Test/Kha/make.js krom <
But since we want to debug we need the krom.js.temp.map but with above command we get
(node:8803) UnhandledPromiseRejectionWarning: Unhandled promise
rejection (rejection id: 1): Error: ENOENT: no such file or directory, open
krom/krom.js.temp.map'(node:8803) [DEP0018] DeprecationWarning:
Unhandled promise rejections are deprecated. In the future, promise
rejections that are not handled will terminate the Node.js process with a non-zero exit code.
So to fix the first issue of Krom not connecting we should have something like:
"command": "node Kha/make --debug -t krom",
But this is with a git cloned workspace version of Kha; I tried using Kha from KodeStudio but I always had issues because there is apparently no
--debug argument. When trying the solution the CL gives me ie
--inspect I now have an issue with the
Starting inspector on 127.0.0.1:9229 failed: address already in use so using the Kha version of KodeStudio(on linux at least) doesn't seems to work.
When I get Krom running with the git cloned workspace version of Kha the issue is that breakpoints don't get activated while debugging.