Skip to content

fix!: do not keep persistent process by default#743

Draft
sheremet-va wants to merge 12 commits intomainfrom
fix/do-not-keep-process
Draft

fix!: do not keep persistent process by default#743
sheremet-va wants to merge 12 commits intomainfrom
fix/do-not-keep-process

Conversation

@sheremet-va
Copy link
Member

@sheremet-va sheremet-va commented Mar 5, 2026

By default, vscode extension doesn't keep any long-running processes anymore.

  1. Process is spawned to read the config to get files and certain config values
  2. Process is spawned to collect tests in the files, this will also read the config again
  3. Process is spawned to run the test on a button click
  4. Process is spawned to debug the test on a button click
  5. Process is spawned to run tests with coverage on a button click
  6. A long-running process is spawned when "turn on continuous run" button is clicked; it is closed if there are no continuous tests anymore (with a 1s delay in case a user wants to click on another test)
  7. A new "Toggle Vitest Configs" command is added to remove certain tests from the tree (we still have to read the config to resolve the workspace properly) - fixes Allow on the fly toggling of configs #739

Fixes #592
Fixes #512
Fixes #671
Fixes #418
Fixes #648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant