bun + vscode (debugging)?

[Ncage1974]

I'm trying to get bun working with vscode. I do have the extension installed. I am using the nuxt project. Here is the section in launch.json that works when i use npm:

{
      "type": "node",
      "request": "launch",
      "name": "server: npm",
      "outputCapture": "std",
      "program": "${workspaceFolder}/node_modules/nuxi/bin/nuxi.mjs",
      "args": ["dev", "--dotenv", ".env.local"]
   },

Here is how i tried to get it to work with bun

    {
      "type": "bun",
      "request": "launch",
      "name": "server: bun",

      // The path to a JavaScript or TypeScript file to run.
      "program": "${workspaceFolder}/node_modules/nuxi/bin/nuxi.mjs",

      // The arguments to pass to the program, if any.
      "args": ["dev", "--dotenv", ".env.local"],

      // The working directory of the program.
      "cwd": "${workspaceFolder}",

      // The environment variables to pass to the program.
      "env": {},

      // If the environment variables should not be inherited from the parent process.
      "strictEnv": false,

      // If the program should be run in watch mode.
      // This is equivalent to passing `--watch` to the `bun` executable.
      // You can also set this to "hot" to enable hot reloading using `--hot`.
      "watchMode": false,

      // If the debugger should stop on the first line of the program.
      "stopOnEntry": false,

      // If the debugger should be disabled. (for example, breakpoints will not be hit)
      "noDebug": false,

      // The path to the `bun` executable, defaults to your `PATH` environment variable.
      "runtime": "bun",

      // The arguments to pass to the `bun` executable, if any.
      // Unlike `args`, these are passed to the executable itself, not the program.
      "runtimeArgs": []
    },

When i run it with bun it looks like it starts up & vscode is attached but all my breakpoints are disabled & when i try to hit an api on the server this is what i get:

 ERROR  [h3] [unhandled] undefined is not an object (evaluating 'route.length')

  at next (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:44361:21)
  at call (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:16045:7)
  at next (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:35731:9)
  at viteServeStaticMiddleware (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:16718:10)
  at <anonymous> (node_modules/vite-plugin-inspect/dist/index.mjs:737:38)
  at call (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:16039:13)
  at next (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:35731:9)
  at viteServeRawFsMiddleware (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:16734:11)
  at <anonymous> (node_modules/vite-plugin-inspect/dist/index.mjs:737:38)
  at call (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:16039:13)
  at next (node_modules/vite/dist/node/chunks/dep-R0I0XnyH.js:35731:9)
  at processTicksAndRejections (:61:39)

any ideas?

Thanks.....

[malcolmstill]

@Ncage1974 I found that by setting stopOnEntry to true the debugger will stop at breakpoints (noDebug: false doesn't seem sufficient on its own, which I take to be a bug).

[DrTrevor88]

Bun is much harder to debug compared to NodeJS.