I have a Node.js app and all of the breakpoints are unbound. The only thing I did recently was move server.js to /src/server.js and set the output directory in tsconfig.json.

Every file has an unbound breakpoint icon:

Here is my launch.json:

{
   // 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": "node",
         "request": "launch",
         "name": "Launch Program",
         "skipFiles": [
            "<node_internals>/**",
            "public/**"
         ],
         "program": "${file}",
         "trace": true
      }
   ]
}

And tsconfig.json:

{
    "compilerOptions": {
        "target": "ES6",
        "module": "CommonJS",
        "moduleResolution": "node",
        "allowSyntheticDefaultImports": true,
        "resolveJsonModule": true,
        "pretty": true,
        "sourceMap": true,
        "sourceRoot": "src",
        "outDir": "dist",
        "stripInternal": true,
        "noUncheckedIndexedAccess": true,
        "noPropertyAccessFromIndexSignature": false,
        "noEmitOnError": true,
        "useDefineForClassFields": true,
        "forceConsistentCasingInFileNames": true,
        "skipLibCheck": true,
        "esModuleInterop": true
    }
}

Would it be possible for VS Code to mention why the breakpoint failed? Could it list out the path it thinks the files are at? If it can’t find the file for debugging can it describe where and what options to set the correct path?