Inspect through Docker, wrong sourcemap?

[imsergiobernal]

When inspecting throught a docker container, breakpoint behavior looks weird. I think this behavior is done by a wrong source-mapping. image

vscode launch

        {
          "type": "node",
          "request": "attach",
          "name": "Docker: Attach to Node",
          "port": 9229,
          "skipFiles": [
            "<node_internals>/**"
          ],
          "localRoot": "${workspaceRoot}",
          "remoteRoot": "/usr/local/app",
          "sourceMaps": false,
        },

tsconfig.json

{
  "compilerOptions": {
    "allowJs": true,
    "checkJs": false,
    "module": "commonjs",
    "esModuleInterop": true,
    "target": "es6",
    "noImplicitAny": true,
    "moduleResolution": "node",
    "inlineSourceMap": true,
    "inlineSources": true,
    "outDir": "dist",
    "baseUrl": ".",
    "paths": {
      "*": ["node_modules/*", "src/types/*"]
    }
  },
  "include": ["src/**/*"]
}

package.json script (what docker runs) ts-node-dev --files --transpileOnly --watch src/ --inspect=0.0.0.0:9229 -- src/index.ts

[dschuessler]

I second this. If you set a breakpoint at say line 80, the debugger breaks at the code that corresponds to line 80 in the transpiled code, not the source code.

[Beleren]

@imsergiobernal I didn't get it, how does it work if sourceMaps option is not set in tsconfig.json and vscode launch sourceMaps is set to false?

Nevertheless I have the same issue when using debugger attached to docker and it also doesn't generate the .maps inside the container. Breakpoints also doesn't work for some files.

[Seqi]

I had this issue and figured out a solution just now. I fixed this by using the javascript debugger preview. You can achieve this by 2 ways:

• Change "type": "node" to "type": "pwa-node" to force the debugger to use the new javascript debugger
• Set "debug.javascript.usePreview": true, in your vscode configuration

[StrictLine]

@imsergiobernal I didn't get it, how does it work if sourceMaps option is not set in tsconfig.json and vscode launch sourceMaps is set to false?

Nevertheless I have the same issue when using debugger attached to docker and it also doesn't generate the .maps inside the container. Breakpoints also doesn't work for some files.

Any progress on this? For me the type is defaulted to pwa-node, so it cannot be the solution.

I've made some research in other threads:

• the challenge for VSCode is described here at the best (the result of the transpilation is not on your local machine): https://github.com/microsoft/vscode/issues/20355#issuecomment-281782079
• @delfinof also created a git repo for this: https://github.com/delfinof/debugging-in-docker , but I'm not sure if this code is already outdated, your and my case might differ from this scenario: we want to attach to an already running container process and not execute a new one

My test scenario

Attach to a running docker container on my QNAP NAS, where ts-node-dev is running and listening on the port 9229 (by --inspect) on every IP. I manage to attach to the debugger, but the breakpoints seem not to work, I guess, because of the reason mentioned in the previous references above.

@delfinof: I'm sorry to mention you so often, but did you open a new issue back then? https://github.com/microsoft/vscode/issues/20355#issuecomment-281843426