Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to consume Debug Adapter / debugServerMain.ts outside of VSCode?
See original GitHub issueI’m willing to replace the usage of node-debug & node-debug2 modules in Eclipse Wild Web Developer by the newer js-debug module.
However, I didn’t find out how to actually start the debug adapter. For node-debug, I could “extract” the module from VSCode, import it in Wild Web Developer and then run node node-debug2/out/src/nodeDebug.js to start the debug adapter and talk DAP with it; but with js-debug, I don’t know what would be a similar entry point. I tried node ms-vscode.js-debug/src/extension.js but this requires VSCode running apparently. I found the very interesting debugServerMain.ts class but don’t find it in the final distribution in VSCode.
Is there another command I should try? Or is the debugServerMain just removed in the distribution (so I should build vscode-js-debug myself) ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
js-debug is pretty standalone and ships (in an extension) as a set of standalone webpacked js files
That’s right. What would your ideal ‘ready to go’ distribution look like? An npm package?