fix: plugins don't think it's watch mode

[sheremet-va]

Fixes #1003

[wight554]

Is it possible to add some custom meta flag e.g. vitestWatch that'll rely on options.watch so plugins can rely on it for adding watch specific logic?
Would it work for non-pre plugins when added here?

vitest/packages/vitest/src/node/plugins/index.ts

Line 161 in f027b05

if (!options.watch)

[sheremet-va]

Is it possible to add some custom meta flag e.g. vitestWatch that'll rely on options.watch so plugins can rely on it for adding watch specific logic?

Would it work for non-pre plugins when added here?

vitest/packages/vitest/src/node/plugins/index.ts

Line 161 in f027b05

if (!options.watch)

Options are resolved after configResolve, so no it's not possible, and I am tired of answering the same question to you. 🙁

If for some reason plugin wants to do something vitest-specific, it should use VITEST env variable.

[wight554]

Is it possible to add some custom meta flag e.g. vitestWatch that'll rely on options.watch so plugins can rely on it for adding watch specific logic?
Would it work for non-pre plugins when added here?

vitest/packages/vitest/src/node/plugins/index.ts

Line 161 in f027b05

if (!options.watch)

Options are resolved after configResolve, so no it's not possible, and I am tired of answering the same question to you. 🙁

If for some reason plugin wants to do something vitest-specific, it should use VITEST env variable.

Not talking bout vitest specific, but vitest watch specific, but if api design doesn't allow to expose it in any way, then it might be better to kill watch mode at all
Tbh I'd check for possible performance regressions if esbuild vite logic relies on watch mode before merging it
In my own testing I haven't noticed issues when comparing w/ and w/o watchMode with rollup plugin typescript as transformer

[wight554]

Nvm just realized vitest has own watcher instead of relying on vite/transformer, then I see no reason not to merge this one