Menu
Chrome Dev Tools has offered the ability to blackbox selected code for a while now, but I can't seem to find a comparable feature for VSStudio when debugging Node.
I've been through the debugger docs and lots of issues on VSCode's Github, but I can't seem to find an answer.
Is it possible to exclude (for example node_modules/) from debugging?
987
You will first debug code using the built-in Node. js debugger tool, setting up watchers and breakpoints so you can find the root cause of a bug. You will then use Google Chrome DevTools as a Graphical User Interface (GUI) alternative to the command line Node.
Node. js includes a command-line debugging utility. The Node. js debugger client is not a full-featured debugger, but simple stepping and inspection are possible. To use it, start Node.
I haven't tried this I must admit, barely got round to use debugging in vscode just yet, but it does appear that blackbox-ing was supported in v1.8:
https://code.visualstudio.com/updates/v1_8#_node-debugging
We have added a feature to avoid code that you don't want to step through. This feature can be enabled with the skipFiles setting in your launch configuration. skipFiles is an array of glob patterns for script paths to skip.
Files can be exluded using skipFiles in your launch configuration:
"skipFiles": [
"node_modules/**/*.js",
"lib/**/*.js",
"async_hooks.js",
"inspector_async_hook.js"
]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
