vscode-js-debug VS nvim-dap

Now I'm attempting to configure it with just vscode-js-debug, looking at the https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md and trying to configure it with no success.

Maybe this

Chrome 111 breakpoints don't work (github, VS CODE specific)

If you pay attention to the image above you'll notice there are some mumbled log messages there I've filed an issue regarding those on vscode-js-debug In the meantime, if you have too many messages you may want to stick with dev tools

For reference, for debugging Typescript vscode-js is the current debugger used in vscode.

Debugging experience ain't all that great on Emacs when compared to VSCode. VSCode just simply wins here. Due to some technical complications, Emacs doesn't support VSCode js-debugger. It does support an older chrome debugger which might or might not work for most. I honestly didn't test it that much. Also, for a debugging workflow, I find it easier to use a mouse than a keyboard. I have been looking at how I can port the js-debugger to Emacs but I'm not sure if I have the necessary skills (BUT I'd still learn a lot). So for debugging I have been relying on VSCode.

vscode-node2-debug is now deprecated despite being the officially recommended dap adapter. The newer vscode-js-debug isn't dap compatible and doesn't look like it will be. I did see some hacks to make vscode-js-debug work, but I didn't try them myself. Some hacks and the compatibility issues are discussed here

It's a new JS debugger in VS Code, and they made it the default one in June last year.

Thanks for the update u/Amssstronggg; glad you found the culprit extension. Have you reported the problem already to the extension owners at Issues · microsoft/vscode-js-debug (github.com) ? I am sure they would love to take a look and see what's going on. I would also mention the slow extension activation problem there.

There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.

https://github.com/mfussenegger/nvim-dap/issues/1062 https://github.com/mfussenegger/nvim-dap/issues/737

Also, you can set up debugger integration with https://github.com/mfussenegger/nvim-dap .

You could use nvim-dap with nvim-dap-python.

I'd suggest starting with a Neovim distro that makes things work for you and as you get familiar you can transition to a more custom configuration as you see fit. If you want to do it by yourself then the most popular plugin for debugging in Neovim is nvim-dap and there is also an extension for Python to give you a more ready to go config instead of doing it yourself. You should read the docs of those 2 to see how you should customize accordingly your configuration.

(neovim only) nvim-dap

https://github.com/mfussenegger/nvim-dap + https://github.com/theHamsta/nvim-dap-virtual-text should be able to do it, I think?

If you want to debug types in TypeScript, you could use marilari88/twoslash-queries.nvim. If you would like to debug TypeScript/JavaScript code, then you need mfussenegger/nvim-dap, you could read this article: Debugging using DAP to understand how to set up it.