Troubles setting up vs code debugger for Jest

I’m trying to configure the vsCode debugger to debug my jest unit tests. I followed the Nrwl blog post (https://blog.nrwl.io/debugging-nx-in-vs-code-cb1dbe9eeeba) and i can’t get it to work. In fact, after setting up my lunch.json as follows:

{
	"name": "debug-jest",
	"type": "node",
	"request": "launch",
	"program": "${workspaceFolder}/frontends/node_modules/@angular/cli/bin/ng",
	"args": [
		"test",
		"lib-name",
		"--codeCoverage=false",
		"--testNamePattern=test",
		"--testFile=${workspaceFolder}/frontends/libs/test-path"
	],
	"cwd": "${workspaceFolder}/frontends/",
	"console": "internalConsole"
}

the debugger starts and immediately outputs an error:

Exception has occurred: Error
Error: ENOENT: no such file or directory, access 'C:\frontends\node_modules\@angular\cli\models\commands.json'
    at Object.accessSync (fs.js:193:3)
    at Object.existsSync (fs.js:224:8)
    at Object.findUp (C:\frontends\node_modules\@angular\cli\utilities\find-up.js:21:22)
    at Object.runCommand (C:\frontends\node_modules\@angular\cli\models\command-runner.js:50:42)
    at default_1 (C:\frontends\node_modules\@angular\cli\lib\cli\index.js:32:54)
    at Object.<anonymous> (C:\frontends\node_modules\@angular\cli\lib\init.js:120:1)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)

Am I doing something wrong?

[Tre665]

I also had issues to get the debugging working in vscode. The nicest solution that worked for me was the config from @toddwseattle. He shared his config in this gist.

You can also find a discussion in the vscode jest repo here

What this solution makes it super nice is, that it also offers a selection menu for the lib that you want to debug. I think this is pretty handy in a monorepo environment.

[FrozenPandaz]

Hi, sorry about this.

This was mislabeled as stale. We are testing ways to mark not reproducible issues as stale so that we can focus on actionable items but our initial experiment was too broad and unintentionally labeled this issue as stale.