feat: support standalone mode

[sheremet-va]

Description

Closes #5502

This PR adds support for a --standalone CLI flag. When this flag is used, Vitest will ignore file filters and won't run any tests until the file is changed, or the API is called programmatically.

TODO

• Tests

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 ready!

Name	Link
🔨 Latest commit	bd22220
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/6627b4aafe96c40008a623d7
😎 Deploy Preview	https://deploy-preview-5565--fastidious-cascaron-4ded94.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[AriPerkkio]

Is this something that the extension could also use? Or at least make it use less private APIs?

Good place for test would be at https://github.com/vitest-dev/vitest/tree/main/test/watch/test, maybe watch/test/standalone.test.ts. Start Vitest in watch mode, check that it's running, press re-run and check that all expected tests ran.

I quickly tested this locally and didn't get it working:

vitest-standalone.mov

[sheremet-va]

Is this something that the extension could also use? Or at least make it use less private APIs?

Yes, I am adding this mostly because I want to try running debugger with launch instead of attach configuration.

[sheremet-va]

Good place for test would be at main/test/watch/test, maybe watch/test/standalone.test.ts. Start Vitest in watch mode, check that it's running, press re-run and check that all expected tests ran.

I added a .each for the stdin tests since they should all work for both modes (--standalone, --no-standalone)

[AriPerkkio]

$ cd vitest/test/core
$ pnpm run test --standalone

# Press "P" for filename filter
# Type "circular"
# Press enter


> RERUN  change filename pattern
>        Filename pattern: circular
>        Test name pattern: /^((?!does not include test that).)*$/
>
> ✓ |core| test/circular.test.ts (2)
> ✓ |core| test/expect-circular.test.ts (4)
> ✓ |core| test/mocked-circular.test.ts (1)
>
> Test Files  3 passed (3)
>      Tests  7 passed (7)

# Press "A" to re-run all

# Runs only 3 tests, should run all ❌ 
>  RERUN 
> 
>  ✓ |core| test/expect-circular.test.ts (4)
>  ✓ |core| test/mocked-circular.test.ts (1)
>  ✓ |core| test/circular.test.ts (2)
> 
>  Test Files  3 passed (3)
>       Tests  7 passed (7)

Repeat steps above with plain pnpm run test and see how pressing "A" re-runs all tests. ✅

[sheremet-va]

Repeat steps above with plain pnpm run test and see how pressing "A" re-runs all tests. ✅

Should be fixed now. It actually didn't rerun anything even on the first "A".