vscode-js-debug VS vimspector

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.

I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).

The actual title is "Vimspector - A multi-language debugging plugin for Vim".

It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...

vimspector

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

You could try vimspector. It's main target is vim and not neovim.

https://github.com/puremourning/vimspector/

I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).

[0] https://github.com/ycm-core/YouCompleteMe

[1] https://github.com/puremourning/vimspector

[2] https://github.com/dense-analysis/ale

For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.