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
// If the terminal is disposed too early, it will show a
// "Terminal has already been disposed" error prompt in the UI.
// Until a proper fix is found, we can just wait a bit before
// disposing the terminal.
setTimeout(()=>terminal.dispose(),100);
}
.
@connor4312 (from the vscode team, who works on debugging experience) would be happy to add some simple metadata to JS debug terminal environment to make Bun debugging work well.
The text was updated successfully, but these errors were encountered:
This happens because js-debug creates a unix socket / named pipe server that will listen until the associated terminal is closed, and Bun closing the terminal make the server shut down.
We'd love so that both Node and Bun work in the JavaScript debugger, are there any suggestions from the VSCode team on the canonical way to make this work?
What version of Bun is running?
1.1.18
What platform is your computer?
Darwin 24.1.0 arm64 arm
What steps can reproduce the bug?
node
and see how debugger cannot attach to the processWhat is the expected behavior?
Javascript debug terminal can attach to a new node process
What do you see instead?
Javascript debug terminal cannot attach to a new node process
Additional information
This's the cause of the problem -
bun/packages/bun-vscode/src/features/debug.ts
Lines 95 to 132 in d5a118e
@connor4312 (from the vscode team, who works on debugging experience) would be happy to add some simple metadata to JS debug terminal environment to make Bun debugging work well.
The text was updated successfully, but these errors were encountered: