vscode-js-debug
nvim-dap-vscode-js
vscode-js-debug | nvim-dap-vscode-js | |
---|---|---|
10 | 6 | |
1,594 | 246 | |
1.6% | - | |
9.0 | 2.4 | |
7 days ago | 7 months ago | |
TypeScript | Lua | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-js-debug
-
Has anybody gotten vscode-js-debug working with a browser like chrome?
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.
-
Best tools/techniques for debugging JavaScript
Maybe this
-
Any breakpoint, anywhere, breaks debugging in VS2022 v17.5.2 ??
Chrome 111 breakpoints don't work (github, VS CODE specific)
-
Debugging Figma and other packaged Electron apps in Visual Studio Code
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
- looking for help - Debug Typescript in vim
-
looking for help - debug typescript
For reference, for debugging Typescript vscode-js is the current debugger used in vscode.
-
Switching From VSCode to DOOM Emacs Recently. Here's My Experience
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.
-
Forks of vscode-node2-debug, node DAP options
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
-
Problem with using Chrome debugger on React in VSCode
It's a new JS debugger in VS Code, and they made it the default one in June last year.
-
Intellicode Slow 3 Seconds
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.
nvim-dap-vscode-js
- [Neovim] Débogage de typeScript dans Neovim avec NVIM-DAP + VSCODE-JS-DEBUG
-
nvim-dap for react frontend development
here my config using https://github.com/mxsdev/nvim-dap-vscode-js to debug on chrome.
- looking for help - Debug Typescript in vim
-
Nvim-DAP debug vite tests with vscode-js-debug?
Yes there is a plugin for this: https://github.com/mxsdev/nvim-dap-vscode-js
-
settings up lunar vim, need help with 2 last things
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
-
Typescript debugging in neovim with nvim-dap + vscode-js-debug
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.
What are some alternatives?
nvim-dap - Debug Adapter Protocol client implementation for Neovim
nvim-dap-python - An extension for nvim-dap, providing default configurations for python and methods to debug individual test methods or classes.
asciidoctor-vscode - AsciiDoc support for Visual Studio Code using Asciidoctor
lvim - My config for LunarVim
vscode-cointy - Welcome to Cointy, a vs code extension for checking cryptocurrency prices as you code.
edamagit - Magit for VSCode
vscode-sftp - Super fast sftp/ftp extension for VS Code
debug - A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers
crosshair-vscode - Use crosshair to statically analyze Python code from within VS Code.
tig - Text-mode interface for git