How can VS Code's JavaScript Debug Terminal be coerced into stepping into node's internal JavaScript files (Ex. the http
module to step into the createServer
function, for example)? There are many questions and answers about how to skip node internal files, but my question is the opposite.
I've tried:
"debug.javascript.terminalOptions": {
"skipFiles": [
"<node_internals>/**/*.cc"
]
},
(I know the VS Code debugger can't jump into c++ code, so I just tried this in hopes that the .js files wouldn't match the pattern)
"debug.javascript.terminalOptions": {
"skipFiles": []
},
"debug.javascript.terminalOptions": {
"skipFiles": [
"!<node_internals>/**"
]
},
and not inserting any debug.javascript.terminalOptions
, VS Code still steps over calls to node internals. It seems like skipping node internal files is a hardcoded setting.
In order for VS Code to honor new settings for
"debug.javascript.terminalOptions": {
"skipFiles": [
"!<node_internals>/**"
]
}
You must execute the Developer: Reload Window
command. It works that way on standalone linux as well, so it's not WSL2-specific.
"skipFiles": []
does work as well.