nvim-dap-vscode-js VS vscode-js-debug

here my config using https://github.com/mxsdev/nvim-dap-vscode-js to debug on chrome.

Yes there is a plugin for this: https://github.com/mxsdev/nvim-dap-vscode-js

I am also currently in the process of figuring out how DAP works for next.js remix.run. My current dap configuration (https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#Javascript) lets me debug simple express apps but I haven't had any luck outside of that. Have you tried https://github.com/mxsdev/nvim-dap-vscode-js ? Would love to know if anyone else has it figured it out as well

The recommended way to debug node applications is using the vscode-node-debug-2 adapter. However I have failed to make this work with typescript files. The solution that worked for me is a bit hidden in the nvim-dap wiki. I now use vscode-js-debug instead. Following the instructions on this repo (nvim-dap-vscode-js) was pretty straight forward for me and immediately worked like a charm.

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.