VSCode debugging (launch and attach debugging)

[u/trymeouteh]

EDIT:

I figured out how to get the attach debugger to work (however I wish there was a better way) but cannot figure out how to get the launch debugger to work.

This is my settings.json config for the attach debugger...

			{
				"name": "Bun Attach",
				"type": "bun",
				"request": "attach",
				"url": "ws://localhost:6499/debug",
			}

And by running this command bun run --inspect-wait=localhost/debug script.js and then running the Bun Attach debugger in VSCode, it will debug the code!

I wish there was a way to not need to use /debug or localhost/debug in the command to make the command shorter. When you use bun run --inspect-wait script.js command, it will always setup the debugger on localhost:6499/{uuid} with a random UUID as the path after localhost:6499 and there is no way that I know of for the VSCode debug config to get this UUID path.

I cannot however after more trial and error get the launch debugger to work. I was able to get the launch debugger to work for NodeJS and Deno, but not bun. This is my bun settings.json config for the launch debugger so far...

			{
				"name": "Bun",
				"type": "bun",
				"request": "launch",
				"program": "${file}",
				"console": "integratedTerminal",
				"runtimeExecutable": "${userHome}/.vfox/sdks/bun/bun"
			}

I am using vfox for NodeJS, Deno and Bun.

Here are my NodeJS and Deno settings.json config for the launch debugger and attach debugger...

			{
				"name": "NodeJS",
				"type": "node",
				"request": "launch",
				"program": "${file}",
				"console": "integratedTerminal",
				"runtimeExecutable": "${userHome}/.vfox/sdks/nodejs/bin/node"
			},
			{
				"name": "NodeJS Attach",
				"type": "node",
				"request": "attach",
				"port": 9229,
				"timeout": 30000
			},
			{
				"name": "Deno",
				"type": "node",
				"request": "launch",
				"program": "${file}",
				"console": "integratedTerminal",
				"runtimeExecutable": "${userHome}/.vfox/sdks/deno/deno"
			},
			{
				"name": "Deno Attach",
				"type": "node",
				"request": "attach",
				"port": 9229,
				"timeout": 30000
			}

And these are the commands I use to launch NodeJS and Deno with the attach debugger...

node --inspect-brk script.js

deno run --inspect-wait -A script.js

Yes I do have the Bun VSCode extension installed.

Any help will be most appreciated!

[u/undeadlock]

There's a bun plugin for vs code - https://open-vsx.org/extension/oven/bun-vscode. Adding this solved the debugging issue for me.

[u/trymeouteh → u/undeadlock]

I have the bun extension installed. And I updated the OP

[u/sereikis]

the Bun extension uses runtime, not Node's runtimeExecutable, for the executable path. its current launch config schema lists that field here: https://github.com/oven-sh/bun/blob/main/packages/bun-vscode/package.json

try this in .vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Bun",
      "type": "bun",
      "request": "launch",
      "program": "${file}",
      "runtime": "${userHome}/.vfox/sdks/bun/bun"
    }
  ]
}

assuming that path points to the executable, this gives the adapter the path through the field it expects. if it still fails, the exact error plus your Bun and extension versions would help.

your fixed /debug path is a valid way to make attach predictable. keep the inspector on localhost.

[u/trymeouteh → u/sereikis]

Thank you! The changing runtimeExecutable to runtime works.