vscode-js-debug VS VSpaceCode

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.

Try VSpaceCode.

I use the extension package called VSpaceCode keeps my hand on the keyboard 90% of the time.

I can highly recommend VSpaceCode: https://vspacecode.github.io/

VspaceCode might help you and others: https://vspacecode.github.io/

What has helped me with the consolidation is the ubiquity of my preferred key bindings. I use vim keys with spacemacs like bindings.

On emacs, doom-emacs[1] gives me the bindings. On VSCode, VSpaceCode[2], on Jetbrains Rider, Intellimacs[3]. While there are minor differences between the implementations, I have very limited friction when switching between IDEs.

I have paid for the Jetbrains ultimate subscription as I also use DataGrip. I think I’ll be satisfied with the current version of their IDEs for the next 2 years even if I decide to cancel the sub.

[1]: https://github.com/doomemacs/doomemacs

[2]: https://vspacecode.github.io/

[3]: https://github.com/MarcoIeni/intellimacs

For setting up VSCode as a modal editor with mnemonic keys use https://vspacecode.github.io/. It wont be as good as doom/spacemacs but its for sure better than VSCode vanilla

Productivity is purely subjective and the most minimal and customizable solution is not always the answer. My personal solution is doom emacs for productivity with org mode, text authoring with latex / pandoc and random text editing and VSCode with VSpaceCode for coding.

try VSpaceCode

Then Spacemacs is probably the most nicely configured editor in existence. It improves over Vim by making the SPC the central leader key, and adding highly intuitive mnemonic keybindings. Really, check out Spacemacs for 5 minutes, and I guess you will understand the beautiful concept and using it you will have the power of Emacs and Vim combined (and improved on) in one. You should not just take my words without checking them, but I can tell you that I have checked out the various 'Spacemacs imitations', spacevim, vspacecode, atom with which-key, but they all pale by comparison to Spacemacs (Doom emacs is a good competitor but personally I prefer Spacemacs and definitely I would recommend it over Doom for beginners).