DAP documentation required, and is anybody using dap with Helix?

[mabasic]

I have just spend an entire day trying to figure out how to use debug with Helix ... still no success.

I am trying to configure https://github.com/microsoft/vscode-js-debug so that i can debug Deno programs.

This is what I have so far:

[language.debugger]
name = "test"
transport = "stdio"
quirks = { absolute-paths = true }
command = "node"
args = ["/home/mabasic/bin/js-debug/src/dapDebugServer.js", "8123"]

[[language.debugger.templates]]
type = "pwa-node"
name = "source"
request = "launch"
completion = [ { name = "main", completion = "filename", default = "index.js" } ]
args = { program = "{0}", runtimeExecutable = "deno", runtimeArgs = ["run", "--unstable-kv", "--inspect-wait", "--allow-all"], attachSimplePort = "9229" }

it returns request 0 timed out when I do ctrl g l and then select "source".

I have managed to start the dap in a separate terminal and use :debug-remote 127.0.0.1:8123 and it would connect, but the dap would respond with config unknown or something like that every time in the terminal. I have tried changing everything that I could find. I have tried changing to "tcp", but it complains about incorrect transport...

Can somebody help with this?

What are the available options and what do they do and what values can I enter and why. So much unknown.

This is my reference:

• https://github.com/sigmaSd/deno-nvim
• https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#javascript-deno

[tye-exe]

Did you ever find an answer as I'm experiencing the same issue?
Might have to switch to vim or Neo-vim if i can't get the debugger to work.

[Kurren123]

@mabasic any update on what you did?

[mabasic]

Nope. Haven't tried again since. But as a workaround I have used the browsers built in v8 debugger to debug deno. Start deno in debug mode then open developer tools in the browser and you will see a green node js button. Once you click on that a debugger will attach to the deno process

[Kurren123]

Thanks. Won't help me much with C# debugging however!

[deriamis]

I think you might be somewhat confused here. vscode-js-debug only communicates via TCP, not stdio, so the configuration you have won't work. You also likely want to let Helix substitute a random port for you, which you can do with a template. This is what I have, from the built-in configuration:

[[language]]
name = "javascript"

[language.debugger]
name = "vscode-js-debug"
transport = "tcp"
command = "node"
args = [ "~/.local/libexec/vscode-js-debug/src/vsDebugServer.js" ]
port-arg = [ "{}" ]

[[language.debugger.templates]]
name = "attach"
request = "attach"
completion = [ "pid" ]
args = { mode = "local", processId = "{0}" }

[[language.debugger.templates]]
name = "source"
request = "launch"
completion = [ { name = "main", completion = "filename", default = "index.js" } ]
args = { program = "{0}" }

Note, however, that recent versions of vscode-js-debug might not work right now due to an unimplemented reverse request type. Also, you can likely add other debugger templates to, for example, connect to the DAP from a browser so you can test it live.

[jasonwilliams]

Please see this thread #11906