Dr. David A. Kunz

Hi @mfussenegger , Thanks a lot for your response, > Wasn't this fixed in https://github.com/mfussenegger/nvim-dap/issues/343 ? It seemed to work at the time of #343 , but now there are...

Thanks a lot for the information @entropitor and @mfussenegger ! Regarding Jest: I also noticed ignored breakpoints, the reason for this is that there's some source code manipulation and the...

I see, seems like a lot of trouble with `vscode-js-debug`, I think I'll stick to `node-debug2` for now. Regarding the processes: As a workaround, I will close the current process...

Will try immediately!

It seems to work (I restarted a debugging session ~10 times and don't have any more Node.js processes). There is only a problem when I spam debugging processes (starting the...

Hi @mfussenegger , Thanks for looking into it! Minimal Example: File: test.js ``` console.log('after') debugger console.log('after') ``` Lua configuration for node2: ```lua dap.adapters.node2 = { type = 'executable', command =...

If I perform ```lua _G.test_dap = function() local dap = require'dap' dap.terminate(nil, nil, function() vim.wait(2000, function() dap.run({ args = { "--no-cache" }, console = "integratedTerminal", cwd = "your-cwd", --

Oh I see, sorry for not reading the documentation. It waits until the callback is done - I thought it would wait and then call the callback... let me check...

Okay, with the following ```lua _G.test_dap = function() local dap = require'dap' dap.terminate(nil, nil, function() vim.wait(2000, function() local session = dap.session() return session and session.initialized end) dap.run({ args = {...

Hi @ayoubelmhamdi , Thank you very much for this PR, really appreciated! But I'm not sure if we should put this information in the `README` as this list can be...