-
Notifications
You must be signed in to change notification settings - Fork 146
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
Debugger not working, Unable to retrieve source content from standard library #233
Comments
I'm getting this error with the sample web server from the manual https://deno.land/manual/examples/http_server
|
For me debugger is working but debugger stops at Sometimes debugger shows filenames like |
@algiuxass Have you tried with the |
@David-Else I looked over the notes at the site you suggested, but it didn't help. I can run the debugger. If I step into an import module, I get a popup that says "This is a missing file path referenced by a sourcemap. Would you like to debug the compiled version instead?". If I click "Yes" then I can step through the compiled code. So there are two issues:
Here is my {
"version": "0.2.0",
"configurations": [
{
"name": "Deno",
"type": "pwa-node",
"request": "launch",
"cwd": "${workspaceFolder}",
"runtimeExecutable": "deno",
"runtimeArgs": [
"run",
"-A",
"--inspect-brk",
"${file}"
],
"attachSimplePort": 9229,
"outputCapture": "std"
}
]
} |
I'm in the same boat as @mvolkmann. Same exact questions and problems. |
I just update to Deno 1.7 and got same issue.
|
I get the same problem as @Sharpiro with Deno 1.7.2 with VS code deno plugin v2.3.3. I'm using WSL 2. Any fixes? |
I got a similar problem for debug my tests here... but I can continue running the debugger after click Deno v.1.7.2 My lauch.json: {
"version": "0.2.0",
"configurations": [
{
"name": "Test Deno",
"request": "launch",
"type": "pwa-node",
"cwd": "${workspaceFolder}",
"runtimeExecutable": "deno",
"runtimeArgs": [
"test",
"--inspect-brk",
"--config",
"tsconfig.json"
],
"outputCapture": "std",
"attachSimplePort": 9229
}
]
} |
To all people in this thread, you seem to be having two different issues. One of them is that the inspector is pausing everytime you start it, forcing you to resume it as is the case of @edualb . That can be easily fixed by not using The second one is the fact that the inspector can't debug remote code correctly, causing the |
@Soremwar At least for me the |
@Alqio What is the command you are using to run the code? Are you using a |
You were actually correct I believe, because removing --inspect-brk removes the problem. However, does that mean it's impossible to debug a deno project? |
@Alqio No, as I explained above it's quite easy to debug your project. However there is currently a limitation when debugging third party code (url imports) that causes the error that you commented earlier, but putting breakpoints in your own code (even with url imports) works just fine. |
This is related to denoland/deno#11874. I believe fixing the source maps will fix this issue. |
I believe this is now fixed, since debugger in Deno can handle source maps without a problem. Please let me know if the issue persists with latest Deno version. |
I press f5 in
mod.ts
to debug, choose deno, but then a file calledcolors.ts
appears with:Could not load source '/home/xx/workspace-directory/std@0.70.0/fmt/colors.ts': Unable to retrieve source content.
The repo is https://github.com/David-Else/eslint-config-octopus and video:
Versions
vscode: 1.49.1
deno: 1.4.1
extension: 2.3.1
The text was updated successfully, but these errors were encountered: