Visual Studio Code creating breakpoints with auto attach disabled in NodeJS Application
I recently read this article which speaks on a new feature of VS Code that auto attaches on Node processes. I turned this on in the settings to try it out but after disabling it, it still seems to run on its own. Or perhaps, this has nothing to do with the phenomenon that is occurring.
What's happening is that when I start my server with VS Code (using NodeJS launch configuration) after a few minutes of runtime, VS Code sets a breakpoint (phantom?) on a seemingly random line of code. It could either be something like server side JavaScript or even a Node Module like Azure App Insights. There isn't really any rhyme or reason to why/where the breakpoint is being set.
I have some theories:
- I enabled the auto attach setting and because it is new, disabling it does not work somehow. Maybe I discovered a bug with it.
- My code sucks so much that VS Code doesn't want to continue to run it. It pauses on certain parts of the code because it is getting hung up on something.
- I set breakpoints at some of these locations previously (some, not all) and they are being set because of some caching issue.
Here are some screenshots to help visually understand what I am witnessing:
VS Code Screenshot auto attach/phantom debug
Here is my .vscode/launch.json configuration:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}node.js visual-studio-code vscode-debugger
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
add a comment |
I recently read this article which speaks on a new feature of VS Code that auto attaches on Node processes. I turned this on in the settings to try it out but after disabling it, it still seems to run on its own. Or perhaps, this has nothing to do with the phenomenon that is occurring.
What's happening is that when I start my server with VS Code (using NodeJS launch configuration) after a few minutes of runtime, VS Code sets a breakpoint (phantom?) on a seemingly random line of code. It could either be something like server side JavaScript or even a Node Module like Azure App Insights. There isn't really any rhyme or reason to why/where the breakpoint is being set.
I have some theories:
- I enabled the auto attach setting and because it is new, disabling it does not work somehow. Maybe I discovered a bug with it.
- My code sucks so much that VS Code doesn't want to continue to run it. It pauses on certain parts of the code because it is getting hung up on something.
- I set breakpoints at some of these locations previously (some, not all) and they are being set because of some caching issue.
Here are some screenshots to help visually understand what I am witnessing:
VS Code Screenshot auto attach/phantom debug
Here is my .vscode/launch.json configuration:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}node.js visual-studio-code vscode-debugger
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
add a comment |
I recently read this article which speaks on a new feature of VS Code that auto attaches on Node processes. I turned this on in the settings to try it out but after disabling it, it still seems to run on its own. Or perhaps, this has nothing to do with the phenomenon that is occurring.
What's happening is that when I start my server with VS Code (using NodeJS launch configuration) after a few minutes of runtime, VS Code sets a breakpoint (phantom?) on a seemingly random line of code. It could either be something like server side JavaScript or even a Node Module like Azure App Insights. There isn't really any rhyme or reason to why/where the breakpoint is being set.
I have some theories:
- I enabled the auto attach setting and because it is new, disabling it does not work somehow. Maybe I discovered a bug with it.
- My code sucks so much that VS Code doesn't want to continue to run it. It pauses on certain parts of the code because it is getting hung up on something.
- I set breakpoints at some of these locations previously (some, not all) and they are being set because of some caching issue.
Here are some screenshots to help visually understand what I am witnessing:
VS Code Screenshot auto attach/phantom debug
Here is my .vscode/launch.json configuration:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}node.js visual-studio-code vscode-debugger
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
I recently read this article which speaks on a new feature of VS Code that auto attaches on Node processes. I turned this on in the settings to try it out but after disabling it, it still seems to run on its own. Or perhaps, this has nothing to do with the phenomenon that is occurring.
What's happening is that when I start my server with VS Code (using NodeJS launch configuration) after a few minutes of runtime, VS Code sets a breakpoint (phantom?) on a seemingly random line of code. It could either be something like server side JavaScript or even a Node Module like Azure App Insights. There isn't really any rhyme or reason to why/where the breakpoint is being set.
I have some theories:
- I enabled the auto attach setting and because it is new, disabling it does not work somehow. Maybe I discovered a bug with it.
- My code sucks so much that VS Code doesn't want to continue to run it. It pauses on certain parts of the code because it is getting hung up on something.
- I set breakpoints at some of these locations previously (some, not all) and they are being set because of some caching issue.
Here are some screenshots to help visually understand what I am witnessing:
VS Code Screenshot auto attach/phantom debug
Here is my .vscode/launch.json configuration:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch",
"program": "${workspaceFolder}\bin\www",
"envFile": "${workspaceFolder}/.vscode/config.env"
}
]
}node.js visual-studio-code vscode-debugger
node.js visual-studio-code vscode-debugger
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
asked Nov 22 '18 at 18:44
Al RamseyAl Ramsey
86
86
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436646%2fvisual-studio-code-creating-breakpoints-with-auto-attach-disabled-in-nodejs-appl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436646%2fvisual-studio-code-creating-breakpoints-with-auto-attach-disabled-in-nodejs-appl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
