Elliott Shugerman

Reading through [this thread](https://github.com/microsoft/vscode-js-debug/issues/902) (which OP @pretentious7 posted above) and you'll find that currently `vscode-js-debug` uses a relatively complicated mechanism to interface with VS Code, and this mechanism is not...

@danilevy1212 Yes, see https://github.com/emacs-lsp/dap-mode/issues/369. In the meantime you can manually build and install `node-debug2`, as described above: https://github.com/emacs-lsp/dap-mode/issues/554#issuecomment-1171256089.

Now that treesitter is a thing I'm not really interested in this anymore, so I'm gonna close it. Feel free to reopen.

Sweet, thanks for tackling this! I'll try it out ASAP. > I have to decide whether we want/need the support for hierarchical debug sessions and I am not 100% sure...

Ah cool! I'll try that out then, hopefully later today!

> Initial support is posted here: https://github.com/emacs-lsp/dap-mode/pull/733 > > For those who want to test: I have downloaded the version from here: https://github.com/microsoft/vscode-js-debug/issues/1388#issuecomment-1505547178 . Then you have to adjust dap-js-debug-program...

Good stuff! I'll stick with this for the next few days of work keeping those points in mind and get back to you with a more in-depth testing report.

@yyoncho I've continued to run your branch over the past couple weeks and again overall it's working nicely, but > - session management works fine(e. g. cleanup after child session...

Thanks for the PR! I hope to take a closer look and test later this week. One minor reservation I have is that, best I can tell, pg_dumpall does not...

OK, great, please do!