Is it possible to debug with Bun's inspect?

[ckhatton-pvfscaffolding]

I have a VS Code launch file.

.vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "chrome",
      "request": "launch",
      "name": "client: chrome",
      "url": "http://localhost:3000",
      "webRoot": "${workspaceFolder}"
    },
    {
      "type": "node",
      "request": "launch",
      "name": "server: pylon (bun)",
      "runtimeExecutable": "bun",
      "runtimeArgs": ["--inspect=9229"],
      "cwd": "${workspaceFolder}",
      "args": [".pylon/index.js"],
      "env": {
        "PORT": "3000"
      },
      "outputCapture": "std",
      "console": "integratedTerminal"
    }
  ],
  "compounds": [
    {
      "name": "fullstack: pylon",
      "configurations": ["server: pylon (bun)", "client: chrome"]
    }
  ]
}

When I run "server: pylon (bun)" the terminal provides an inspect URL to open in the browser, but when you load it there are no source files. I appreciate it is just using the one file .pylon/index.js, but that one file doesn't load in the devtools.

The same occurs without the launch.json (bun --inspect run .pylon/index.js).

The app itself loads fine.

Is there a way to debug the app?

[schettn]

Hi @ckhatton-pvfscaffolding! Seems like a Safari issue.

Chrome:

Safari:

ref: oven-sh/bun#8628

[schettn]

Inspecting the bundled .pylon/index.js isn't ideal tho because you will lose the file structure. Do you know if the inspector can recreate it with source maps?

[ckhatton-pvfscaffolding]

Hey @schettn, thanks for getting back to me. I tried Chrome like you have shown, thinking maybe it's my Opera GX, but still no joy... Maybe it's because I am on Windows using WSL.

Yeah, usually source maps would recreate it - adding a breakpoint on a file, flings you to the original file.