I was able to get it to work with the following launch configuration:

```json
{
    "name": "Run Mocha",
    "type": "node",
    "request": "launch",
    "program": "${workspaceRoot}/node_modules/mocha/bin/_mocha",
    "args": [
        "--no-timeouts",
        "--require",
        "ts-node/register",
        "${workspaceRoot}/src/**/*.spec.ts"
    ],
    "cwd": "${workspaceRoot}",
    "protocol": "inspector"
}
```

I also had to set `module` as `commonjs` in my `tsconfig.json`:

```json
{
  "compilerOptions": {
    "module": "commonjs",
  }
}
```

### Here's an [example repo][2] with all the files setup correctly

[![Debugging Example][1]][1]



**Further Reading**

* [Issue with mocha test debugging from typescript][3]
* [Running Mocha with TypeScript][4]

[1]: https://i.stack.imgur.com/9Cyrg.png
[2]: https://github.com/KyleMit/debug-mocha-typescript
[3]: https://stackoverflow.com/q/52357172/1366033
[4]: https://www.hossambarakat.net/2017/06/01/running-mocha-with-typescript/

I have started developing a Node/ExpreeJS project in TypeScript.
I should note that I am not running node directly. I am running node in a docker but I do not see any reason that this would be an issue.

I am using vscode as my editor and I am trying to configure a debug launch config for Mocha tests.

My launch configuration is

    {
        "type": "node",
        "request": "launch",
        "name": "SK - Mocha Tests",
        "cwd": "${workspaceRoot}",
        "runtimeExecutable": "make",
        "runtimeArgs": [
            "test-brk"
        ],
        "port": 9321,
        "console": "integratedTerminal",
        "internalConsoleOptions": "neverOpen",
        "protocol": "inspector",
        "sourceMaps": true,
    }

The `make test-brk` command simply maps to a `docker exec` command that executes `npm run test-brk` within the container.

My package.json contains this script definition for `test-brk`

`"test-brk": "mocha --require source-map-support/register --require node_modules/ts-node/register --inspect-brk=0.0.0.0:9222 --debug-brk --exit test/**/*.spec.ts"`

Running the `SK - Mocha Tests` debug task from vscode launches Mocha and runs the tests as expected.
The inspect server is started and the vscode debugger successfully connects as can be seen in the output below.

    $  cd /home/andrew/workspace/service-kit/sk-base-nodejs ; /usr/bin/make test-brk 
    (docker exec node npm run test-brk)
    
    > sk-base-nodejs@0.0.1 test-brk /workspace
    > mocha --require source-map-support/register --require node_modules/ts-node/register --inspect-brk=0.0.0.0:9321 --debug-brk --exit test/**/*.spec.ts
    
    Debugger listening on ws://0.0.0.0:9321/d696c7a4-c4e1-4212-af85-ab1675856a7a
    For help, see: https://nodejs.org/en/docs/inspector
    Debugger attached.
    HTTP server listening on port 8080
    
    
      Hello World
        ✓ should return 200 and Hello World
    
    
      1 passing (34ms)
    
    Waiting for the debugger to disconnect...

However breakpoints are not being hit.
I have set in both the application TS source and the test TS source.
When the tests are running the breakpoints grey out and show

> Breakpoint ignored because generated code not found (source map problem?)

I understand that this is a source map issue between the source TS and the JS being executed for the tests.
As above I am using ts-node with Mocha there seems to be a problem because ts-node does not generate source map files for vscode to read.
This is described in [ts-node/issues/46][1] however there is no solution in that issue. It ultimately links to [vscode-chrome-debug-core/issues/533][2] which reports that it is fixed in a previous release of vscode.

There is also [vscode/issues/3144][3] which suggests transpiling the TS tests into JS and then executing the JS.. but this doesn't allow debugging the source TS.

I would greatly appreciate any input to point me in the right direction.


  [1]: https://github.com/TypeStrong/ts-node/issues/46
  [2]: https://github.com/microsoft/vscode-chrome-debug-core/issues/533
  [3]: https://github.com/microsoft/vscode/issues/3144