-
vscode-node-debug2
Discontinued A VS Code debug adapter that supports debugging Node via the Chrome Debugging Protocol.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
After doing some digging, I can replicate this error by trying to run npm run build on the vscode-node-debug2 package even when I git clone it to its own folder completely outside of neovim. Any thoughts on what's wrong here?
Yeah, I'm aware of that, but this seems to be different. I'm also experiencing some breakpoints not being hit, although I suspect this isn't a Vimspector problem. Using the debugger in VS Code (which I think uses vscode-js-debug) with the exact same code and breakpoint locations doesn't have these problems. I noticed the issue you created on migrating to vscode-js-debug, but I recognize the additional problems that has with the undocumented protocol extensions.
Related posts
-
Vimspector – the Vim debugger rules all
-
Vimspector – the Vim debugger rules all
-
Teaching Vim to your children
-
IDE vs. text editor like notepad++ question for coding with a language's API. Is my understanding of the differences correct, and which is better for beginners?
-
Command line based debugger for C# running on .NET 6