edamagit VS vscode-js-debug

Edamagit for VSCode, the Magit clone I started as a COVID lockdown project, is now seeking a maintainer. I can no longer support this project, but I believe both the users and the project deserve a chance to thrive under the guidance of someone willing and capable.

Lately, my only contributions have been to protect the extension from breaking changes in VSCode and to address critical bugs. I rely on this tool and use it daily, so I will continue to do so unless there's a change in maintainership.

[ Seeking maintainer. Contact [email protected] ]

https://github.com/kahole/edamagit

> Using the Vscode extension version [...]

Are you referring to https://github.com/kahole/edamagit ?

There is a magit inspired extension for VSCode called edamagit. Last I tried it the bare basics were there, but things quickly fell apart when I tried doing anything more than staging a chunk and committing it. But I would image it’s only been getting better over time.

One alternative would be to just not use the mouse with VS Code. For committing, there’s https://github.com/kahole/edamagit where Alt-x c c Ctrl+c Ctrl+c gets you there. Same goes for opening files, etc.

Example where you can see the raw button on the right: https://github.com/kahole/edamagit/blob/develop/tsconfig.json

Not at all - pretty much the opposite: I switched to VS Code after using Emacs (Spacemacs and later Doom Emacs) for 4.5 years. Other than the excellent keyboard usability, I've always found emacs to be a bit of a pain. After I found Edamagit and VSpaceCode, I was sold.

Repo here: https://github.com/kahole/edamagit

I use this for git interactions in VSCode

https://github.com/kahole/edamagit

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.