TypeScript and Jest - debugger stops only on breakpoints in tests, never in source files

创建于 2019年08月20日 18:34

Hi,

I am using TypeScript and Jest.

I have no issue to get debugger stop on proper line in the test file, but I cannot get it stopped in the source files.

This is my `jest.config.json`:

```

module.exports = {
  collectCoverage: true,
  collectCoverageFrom: ['src/**/*.ts'],
  globals: {
    'ts-jest': {
      tsConfig: {
        sourceMap: true,
        inlineSourceMap: true
      }
    },
  },
  preset: 'ts-jest',
  testEnvironment: 'node',
};

```

Any help?

10 条评论

Elena Pogorelova

创建于 2019年08月20日 18:45

Try changing collectCoverage to false - does it help?

"collectCoverage": false,

If the source file is instrumented for coverage, the generated code can't be mapped to source; it's a well known limitation

Rüdiger Schulz

创建于 2020年02月12日 09:48

If you want to keep that option in your config file, you can turn that off in the run configuration for Jest as well by adding the Jest option `--coverage=false`, ideally in the run configuration template.

Lior Chervinsky

创建于 2023年02月09日 07:18

Also seeing a similar problem -
Debugging a Jest test in IntelliJ -
- Debugger stops at many places before arriving to actual Break Points.
- Mostly stops at places that are not really code (comments, empty lines)
- Arriving to the actual breakpoint, sometimes after 5-9 stops.
- Tried the above suggested solutions - ie.
Adding to Jest config file -

"collectCoverage": false,

Running with

--coverage=false

Also tried -

removing the XDebuggerManager tag in workspace.xml

And setting in tsconfig.json:

"sourceMap": true,
"inlineSourceMap": true.

This happens to many others in my company.

Anandtyagi77

创建于 2019年11月08日 01:49

Elena Pogorelova God bless you for this. I'd been struggling to get this work for days. Thanks.

Dan Dascalescu

创建于 2020年03月03日 14:17

I'm also trying to debug a Jest test in a complex monorepo. I've disabled coverage collection in both ways explained above, but I still can't get the debugger to stop on any line. Instead, WebStorm opens index.js (instead of staying in index.ts), and the debugged goes into a limbo state, when nothing seems to be going on.

This problem only occurred in one file. Another Jest TS from another project would debug fine.

I managed to get the debugger working on the problematic file as well, by deleting workspace.xml.

WebStorm 2019.3.3
Build #WS-193.6494.34, built on February 11, 2020
Runtime version: 11.0.5+10-b520.38 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.3.0-28-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 935M
Cores: 8
Registry:
Non-Bundled Plugins: com.intellij.lang.jsgraphql

Elena Pogorelova

创建于 2020年03月03日 14:28

Please share a sample project the issue can be reproduced with

Dan Dascalescu

创建于 2020年03月04日 15:05

If only it were that easy :( I'm working on a complex project with proprietary code and the issue happens with only one very large file. It happened again after I added a few lines of TypeScript (a type definition) near the top of the file. WebStorm keeps opening the .js file every minute or so, even though I closed the file switched to a different task (but the debugger was still apparently "running" - I hadn't clicked the square button to stop it).

Invalidating caches and restarting didn't help, but removing the XDebuggerManager tag in workspace.xml worked.