You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.1.30-canary.71+af82a446d, VSCode Extension Version v0.0.15
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What steps can reproduce the bug?
Fresh VSCode project with a single code-file
Add the default launch.json config that the debugger suggests by default for bun:
{
// Use IntelliSense to learn about possible attributes.// Hover to view descriptions of existing attributes.// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387"version": "0.2.0",
"configurations": [
{
"type": "bun",
"internalConsoleOptions": "neverOpen",
"request": "launch",
"name": "Debug File",
"program": "${file}",
"cwd": "${workspaceFolder}",
"stopOnEntry": false,
"watchMode": false
},
{
"type": "bun",
"internalConsoleOptions": "neverOpen",
"request": "launch",
"name": "Run File",
"program": "${file}",
"cwd": "${workspaceFolder}",
"noDebug": true,
"watchMode": false
},
{
"type": "bun",
"internalConsoleOptions": "neverOpen",
"request": "attach",
"name": "Attach Bun",
"url": "ws://localhost:6499/",
"stopOnEntry": false
}
]
}
Run the debugger with the "Debug File" configuration in any code file in the project.
What is the expected behavior?
The debugger launches bun and attaches to it and stops at the first breakpoint set.
What do you see instead?
On the debug console I see the following output:
Failed to start debugger.
Program could not be started.
Also, the extension host complains about an invalid debug adapter:
2024-09-29 19:16:10.456 [error] Error: Invalid debug adapter
at c.p (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2012:95)
at c.$acceptDAMessage (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2011:16481)
at S (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1903:14635)
at S.Q (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1903:14401)
at S.M (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1903:13434)
at S.L (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1903:12269)
at u.value (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1903:10964)
at o.B (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:93:732)
at o.fire (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:93:949)
at s.fire (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:123:15085)
at K.onmessage (vscode-file://vscode-app/c:/Users/magnu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1919:8198)
Additional information
No response
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.1.30-canary.71+af82a446d, VSCode Extension Version v0.0.15
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What steps can reproduce the bug?
launch.json
config that the debugger suggests by default for bun:What is the expected behavior?
The debugger launches bun and attaches to it and stops at the first breakpoint set.
What do you see instead?
On the debug console I see the following output:
Also, the extension host complains about an invalid debug adapter:
Additional information
No response
The text was updated successfully, but these errors were encountered: