Open ManfredLange opened 1 year ago
hey @ManfredLange
generally you can influence the debug settings using the jestrunner.debugOptions settings.
you can search for the option in issues and you will find plenty of examples
"jestrunner.debugOptions": {
"args": ["--no-cache"],
"sourcemaps": "inline",
"disableOptimisticBPs": true,
}
but i think you issue is conntect to the tsconfig settings.
best regards tristan
I have a simplistic express application that uses a top-level await.
Typescript is happy. Running the app works fine. Running the tests is fine. I found the setting
jestrunner.jestCommand
to make the latter workHowever, when I use the inline
Debug
command provided by VS Jest Runner, I receive the following error which I haven't been able to resolve just yet:However, module is set to
ESNext
intsconfig.json
already. And when I use the inlineRun
command for the same test, then the output looks as follows:Where do I need to change the configuration to make this work for the
Debug
command as well? Any pointers, suggestions, thoughts, etc. would be highly welcome!A complete repro repository is available at https://github.com/RimuTec/express-testing (Note this repo uses a dev container). The test I'm using is the only test in file
/work/service/src/server.integration.ts
(absolute path inside the dev container).