Vscode-js-debug: Node Debugger not working after updating to June 2020 (version 1.47)

[harshal123]

Describe the bug
Node Debugger not working after updating to June 2020 (version 1.47)

To Reproduce
Steps to reproduce the behavior:
After update when I tried to run a server in debug mode it shows me the "options [retryMiliSeconds] is not supported". Server gets started but debugger points gets disappeared.

Log File

VS Code Version: Replace me!

Additional context
Add any other context about the problem here.

[connor4312]

Can you please collect a log file using the instructions provided in the issue template?

[harshal123]

Hi,

I can see this

Process exited with code 1
C:\Program Files (x86)\Nodist\bin\node.exe c:\work\integration-api\index.js
Debugger listening on ws://127.0.0.1:65181/46baf111-1335-454a-ab78-72ed2dc308aa
For help see https://nodejs.org/en/docs/inspector
the options [retryMiliSeconds] is not supported
(node:3428) [DEP0016] DeprecationWarning: 'GLOBAL' is deprecated, use
'global'
the options [retryMiliSeconds] is not supported

On Thu, Jul 16, 2020 at 7:43 PM Connor Peet [e-mail]
wrote:

Can you please collect a log file using the instructions provided in the
issue template?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-js-debug/issues/631#issuecomment-659440132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF3OBXJOA76GIENPTPU7X3R34DKLANCNFSM4O4JDVAQ
.

[jasonwilliams]

Same for me, its just stopped working since this release, i get "unbound breakpoint" wherever i set it :(
Version: 2020.7.1617

[Doubl3]

Doesn't work anymore as well

• VSCode version

Version: 1.47.2
Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf
Date: 2020-07-15T18:18:50.054Z (1 day ago)

• Command launched in a terminal:

[nodemon] 1.19.4
[nodemon] to restart at any time, enter `rs`
[nodemon] watching dir(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node --inspect-brk=0 --debug=3xxx src/service.js`
Debugger listening on ws://127.0.0.1:3xxx/51879355-9a6a-435e-90a8-f9f84f29c6a7

• Cfg used to debug NodeJS process on VSCode side (this cfg worked with previous VSCode version):

{
      "type": "node",
      "request": "attach",
      "name": "Process name",
      "port": 3xxx
    },

[connor4312]

Can you collect a trace log using these instructions?

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to [email protected]

[jamesgibson14]

Just a couple of things I have noticed since the update (I develop with Meteor 1.10):

1. Auto Attach no longer works (it never connects), I have to use the command "Attache to Node Process"
2. Every new terminal (bash) I open runs a debugger by default, I use a lot of terminals so this is a bug for me.
3. I ran across this error with one of my Meteor apps which cause it to fail: Error: Meteor cannot currently handle quoted NODE_OPTIONS

[connor4312]

@jamesgibson14 see https://github.com/microsoft/vscode/issues/102057#issuecomment-657728467. You can reset this behavior by:

1. Making sure you're in 1.47.2
2. Toggling auto attach to "disabled" and then back "on" (if you'd like to use it)

[connor4312]

Also @Doubl3 I notice you have some args --inspect-brk=0 --debug=3xxx. Try removing these and seeing if that works for you; we no longer need these to be able to debug processes.

If you do _need_ to attach to that exact port, then you can use attachSimplePort https://github.com/microsoft/vscode-js-debug/issues/586#issuecomment-658958272

[jamesgibson14]

@connor4312 thanks, I changed those configurations and so far the auto attach seems to be working again.

[illusional]

Piggybacking on this issue, the update broke my node (TypeScript) debugging too:

For me, it couldn't find a module:

Cannot find module "mongodb-extjson"

launch.json

{
    "type": "node",
    "request": "launch",
    "name": "Launch Program",
    "program": "${workspaceFolder}/dist/server.js",
    "preLaunchTask": "tsc: build - tsconfig.json",
    "outFiles": [
        "${workspaceFolder}/dist/**/*.js"
    ],
    "env": {
        "NODE_ENV": "development"
    }
},

Launching in Version: 1.46.1 works fine, but the June update broke it specifically. I'm still able to run through the command line, but debugging is broken.

[connor4312]

Can you collect a trace log using these instructions? https://github.com/microsoft/vscode-js-debug/issues/631#issuecomment-660149131

[illusional]

Hmm, I downgraded and reupgraded and it's now working. So I'll retract my original statement. Not really sure why but glad it's working now.

[connor4312]

Okay, thanks for the info. I suspect the issue was not related to the debugger, perhaps some environment or caching problem somewhere.

[sageguy09]

Worth noting we are seeing an issue as well. We use NPM and have a a debug run-script that looks like this :

"debug": "cross-env NODE_ENV=development node --nolazy --inspect-brk=5858 index.js"

and a launch.json config like :

    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch via NPM",
            "cwd" : "${workspaceFolder}",
            "runtimeExecutable": "npm",
            "runtimeArgs": [
                "run-script", "debug"
            ],
            "port": 5858
        }
     ]

The debugger doesn't fully attach, our console.log() statements in index.js aren't hit, and breakpoints light up. Looks like the call stack is stuck on cross-env and never hits index.js.

(We are using the NPM configuration listed on the Debug section of VS Code docs.)

Let me know if we can provide any further assistance debugging.

[connor4312]

That issue should be fixed as of VS Code 1.47.2. If you're still seeing it, can you collect a trace log using these steps? https://github.com/microsoft/vscode-js-debug/issues/631#issuecomment-660149131

[sageguy09]

Issues (while using the configuration listed above) are still ongoing. I have emailed the trace file requested.

[connor4312]

Thanks for the log!

I think I already fixed your issue as part of https://github.com/microsoft/vscode-js-debug/commit/540fbcace9eda0c43fa0b73797d3cba95a2f443b. I think both of these solutions will work for you:

1. Use the nightly build
2. Remove --inspect-brk from your npm script (we can attach without it; I've updated the docs to reflect that in https://github.com/microsoft/vscode-docs/commit/26b07f527e9862827492aa8fb604dec13a5ef824)

[connor4312]

Closing this as we've not heard back from the author with details.