Vite starts watcher, even if --watch is false

[sheremet-va]

Describe the bug

When Vitest starts in run mode, watcher is initiated and later stopped. In this time watcher can start watching a lot of files.

We should probably not even initiate chokidar watcher. To do this, we need to pass down watch: { ignored: ['*'] } to createServer.

There is a problem that watch and run flags can be configured inside vite.config, which is resolved after createServer call. We should disable this, and allow --watch and --run to be configured only as CLI flags. This way we can determine watch mode before calling createServer. This would be a breaking change.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-q5uxuk?file=README.md&initialPath=__vitest__

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[silverwind]

There is a problem that watch and run flags can be configured inside vite.config, which is resolved after createServer call.

Having these flags in the config is convenient though as I can just npx vite and have it not watch. Can the config be parsed first? Generally I'd say parsing config is the first thing a application should do.