Clear and concise description of the problem

Vitest has great auto-mocking/auto-spying algorithms, which can be used like so:

vi.mock(import("some/module/path"))  // functions do nothing and return undefined
vi.mock(import("some/module/path"), { spy: true })  // functions work normally, but can be manipulated and asserted against

If you want to customize a mocked module, you can do it like so:

vi.mock(import("some/module/path"), async (importOriginal) => {
    const original = await importOriginal()
    const mocked = vi.mockObject(original)
    return {
        ...mocked,
        counter: vi.fn(() => original.counter() + 1)
    }
})

But it is impossible to customize a spied-on module the same way, since there is no spy-version of vi.mockObject().

Suggested solution

vi.mockObject(original, { spy: true })

Note: The function already supports this in its implementation (of course, as it's the one used by vi.mock()):

It's just not exposed to the end-users.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.