vitest-dev
Please bring back auto watch on startup setting
Describe the bug
Please bring back auto watch on startup setting. It was implemented in https://github.com/vitest-dev/vscode/pull/238/commits/82222ab05ba729aba6f568bd6b47a349275a6d31 but disappeared in https://github.com/vitest-dev/vscode/releases/tag/v0.5.0
Reproduction
not relevant
Output
not relevant
Version
1.8
Validations
- [X] Check that you are using the latest version of the extension
- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- [X] The provided reproduction is a minimal reproducible example of the bug.
Aha! I was wondering where this went. Mainly I am used to having VSCode automatically run my tests when I save a test file (using vscode-jest), and I can't figure out how to do that with vitest, other than starting my own watcher terminal and switching to it manually - not a big deal, but it was nicer when vscode automatically started it and showed me the results.
@mltsy You can still do that with the vitest extension. Take a look at the continuous run option: https://github.com/vitest-dev/vscode?tab=readme-ov-file#in-the-testing-view
This issue is about automatically having that option turned on at startup.
If someone wants to contribute this, it should be possible to enable continues run with vscode commands: https://github.com/microsoft/vscode/issues/210848#issuecomment-2499273293
OH wow - that was news to me, thank you! Slightly different workflow, but it works great (and is actually less obtrusive because it doesn't steal focus from the terminal, but does show you the pass/fail in the editor gutter) 🙌 🙏