Open hahanein opened 1 month ago
Vitest uses the default pwa-node
config, and outFiles
is everything in the workspace: https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md#outfiles-1
Does it work if you add them to config.debugExclude
? (This will also override the default value) I can also expose outFiles
- or maybe we should override?
Describe the bug
When there are many large JavaScript files present in a
dist/
directory the debugger will attach, sit there for a long time and terminate unexpectedly.I am using
vitest
as a test runner for a web application. I am not usingvite
. However,dist/
is indeed where all build artifacts are moved to.Of course, most of the files in that directory were stale and should have been removed (automatically). But, the presence of a
dist/
directory in my situation is pure chance. Why isvitest
monitoring this directory as"outFiles"
?In any case, it took many hours for me to spot this error.
outFiles
should be configurable?Reproduction
vitest
installed and a single test moduledist
directory and create many large JavaScript files in themOutput
Version
0.12.4
Validations