-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Debug Mode] Debugger doesn't terminate when code finishes or error **IF** a NPM package is inside deno.lock #16662
Comments
Hi @pietro-lopes I just tried this code and cannot reproduce the problem. What do you mean by "debugger will not close when finishing"? As it is, the debugger never disconnects automatically if it is connected - you have to do so manually by closing the inspector window. Can you please provide the commands you used to get this problem? |
If I have to close manually, how will I know that code really finished or is hanging on some exception like this: Command used are in launch.json from .vscode: "runtimeExecutable": "/home/myusername/.deno/bin/deno",
"runtimeArgs": [
"run",
"--config",
"./deno.jsonc",
"--inspect-brk",
"--allow-all"
],
"attachSimplePort": 9229 |
I missed that you are using VSCode debugger, I was talking about the Chrome DevTools debugger. I'll look into this problem. |
@pietro-lopes just to be completely sure - the problem that you are reporting is that after running the code, "the box" with play/step over/pause/stop buttons is not disappearing. Is that correct? |
Requires denoland/rusty_v8#1134 |
Done, this will be released in v1.28.3 |
Title, and related to #16628
CODE RUNS FINE WITHOUT DEBUGGING
Tested on
In this example code you can attach/launch a debugger with no problem when finishing program
Lock file will contain only remote imports
Here you will add the NPM package noble/hashes to your lock file to run and debugger will not close when finishing
Lock file will contain remote & npm imports
Here you can comment back the NPM package BUT it will still not close debugger.
Lock file will contain remote & npm imports
Only way to fix it is by removing NPM packages from
deno.lock
or delete so it can generates back with only remotes.The text was updated successfully, but these errors were encountered: