vscode jest debug profile with external jest-config

[firsttris]

Holla,
I'm trying to create a jest debug profile with external config.

but i always get the following message:

Error: Can't find a root directory while resolving a config file path.

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug Jest Tests",
            "type": "node",
            "request": "launch",
            "port": 9229,
            "runtimeArgs": [
                "--inspect-brk",
                "${workspaceRoot}/node_modules/jest/bin/jest.js",
                "-i",
                "-t should dispatch GetAccessToken Test",
                "-c ${workspaceRoot}/jest-config.json",  
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        },
    ]
}

while running jest with config from cli is possible, im not able todo this from a vscode debug profile.

on cli you can pass config with -c jest-config.json

any advice?

regards
tristan

[weinand]

@firsttris what do you mean by "external config"?

A "launch.json" will only be found if you open a project folder in VS Code (otherwise there is no ".vscode" folder where the launch.json could live).

BTW, a somewhat simpler and clearer config for jest is:

        {
            "name": "Debug Jest Tests",
            "type": "node",
            "request": "launch",
            "program": "${workspaceFolder}/node_modules/jest/bin/jest.js",
            "args": [
                "-i",
                "-t", "should dispatch GetAccessToken Test",
                "-c", "${workspaceFolder}/jest-config.json"
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }

[firsttris]

Hey @weinand

thx for taking the time to reply to my issue!

with external config i mean external Jest config jest-config.json

if the jest-config is located in package.json i have no issue.

[firsttris]

i updated my debug-profile to the more cleaner version, thx!

no issues running Jest with external jest-config from CLI.

no issues with running VSCode Debug Profile for Jest and Jest-config in Package.json

but Error with VSCode Debug Profile for Jest and Jest-Config in a external file e.g. ./jest-config.json

[weinand]

Does it make a difference if you make the "jest-config.json" relative, e.g.

        {
            "name": "Debug Jest Tests",
            "type": "node",
            "request": "launch",
            "program": "${workspaceFolder}/node_modules/jest/bin/jest.js",
            "args": [
                "-i",
                "-t should dispatch GetAccessToken Test",
                "-c jest-config.json",  
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }

[firsttris]

Same Issue
(already tried all possible variants for absolut & relative paths)

Error: Can't find a root directory while resolving a config file path.
Provided path to resolve:  jest-config.json

[weinand]

@firsttris the error message you are seeing originates from jest, not from VS Code. So you might want to investigate on the jest side as well, e.g. jestjs/jest#3499.

[firsttris]

i thought so as well..

but...

• this issue only happens within a VSCode Debug Profile. not from CLI
• In Webstorm i have also not issue debugging with external jest-config
• A jest config change (like suggested in the issue you liked) won't help since jest can't find the config in the first place

continue investigating on both sides

[weinand]

So where does the jest-config.json actually live?

[firsttris]

jest-config.json is in the ProjectRoot Directory.

i found out if i rename the jest-config.json to jest.config.js

it finds the config without --config (-c) argument

because they setup some default names, to look for:
https://github.com/facebook/jest/blob/master/packages/jest-config/src/constants.js#L16

       {
            "name": "Debug Jest Tests",
            "type": "node",
            "request": "launch",
            "program": "${workspaceFolder}/node_modules/jest/bin/jest.js",
            "args": [
                "-i",
                "-t should dispatch GetAccessToken Test"
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }

for me this workaround is acceptable.

if you don't want to explore further why --config (-c) is not working, we can close this issue

[weinand]

Oh, I think I know what the problem is.
A construct like "-c jest-config.json" must be passed as two separate arguments, e.g. "-c", "jest-config.json". The equivalent "--config=jest-config.json" can be passed as one.

Try this:

        {
            "name": "Debug Jest Tests",
            "type": "node",
            "request": "launch",
            "program": "${workspaceFolder}/node_modules/jest/bin/jest.js",
            "args": [
                "-i",
                "-t", "should dispatch GetAccessToken Test",
                "-c", "jest-config.json"
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }

I will fix my suggestion from above too (so that no one will find a bogus example).

[firsttris]

thanks for your help, your suggestion is working!

now i can update my vscode addon 👍
https://marketplace.visualstudio.com/items?itemName=firsttris.vscode-jest-runner

[weinand]

Great, and sorry for not spotting this earlier.