Simplified module mocking for in-source testing

[sybereal]

I am wondering if it'd be possible to extend the static analysis that checks for import {vi} from "vitest" to also detect const {vi} = import.meta.vitest.

Currently, as far as I understand, module mocking for in-source tests requires globals: true or a top-level ESM import of Vitest. Globals can be problematic, esp. with TypeScript, and importing directly from Vitest in a source file may require finicky build step configuration to avoid emitting that call into a prod deployment.

Since const {...} = import.meta.vitest is already the in-source testing equivalent of import {...} from "vitest" for all other purposes than access to vi.mock(), I would be very happy if that last gap could be filled.

To add some details about our use case: We use in-source testing primarily to test module-internal helpers, with the intent of avoiding exporting these helpers solely to test them. Sometimes, however, such helpers exist because they're wrapping a more general/complex API defined in another module. For the sake of keeping unit tests as encapsulated as possible, we want to mock that external module while testing.

[sheremet-va]

The issue is not with static analysis, it's about the transform that would move vi to the outer scope. Anyway, as far as I know, this should work in Vitest 3+

[sybereal]

The issue is not with static analysis, it's about the transform that would move vi to the outer scope.

Ah, yeah, that makes a lot of sense.

Anyway, as far as I know, this should work in Vitest 3+

Surprising, because the warning in the docs is still there. But true, it does seem to work. I guess I just didn't try it because, as far as I knew, it didn't work before and the warning in the docs was still there.

I wouldn't mind prepping a PR to update the docs in that regard, but I'm not sure I'm 100% clear on the current behavior. Is this a special case for in-source testing, or was the static import restriction relaxed for all modules with Vitest v3?

[sheremet-va]

I wouldn't mind prepping a PR to update the docs in that regard, but I'm not sure I'm 100% clear on the current behavior. Is this a special case for in-source testing, or was the static import restriction relaxed for all modules with Vitest v3?

Mocker now always injects import {} from 'vitest' if vi is not imported locally. Feel free to open PR