Partial Mocking with importActual hanging the tests

[ad1992]

Describe the bug

Hi I am trying to migrate Excalidraw tests currently using Jest to Vitest in excalidraw/excalidraw#6713 and running to issues when mocking

jest.mock("../../scene/export", () => ({
  __esmodule: true,
  ...jest.requireActual("../../scene/export"),
  exportToSvg: jest.fn(),
}));

For this equivalent vite I am using

vi.mock("../../scene/export", async (actual) => {
  const orig = await actual();
  //@ts-ignore
  return { __esmodule: true, ...orig, exportToSvg: vi.fn() };
});

It is getting mocked which I can confirm by adding console.log after the mock but as soon as I am using another module where this mocked function is being called, the tests just hang, I don't see any error so I have to again stop the tests are rerun and its the same result.
For reference this is the file where its being used - https://github.com/excalidraw/excalidraw/blob/master/src/packages/utils.ts#L1 and as you can see the first line imports are what is being mocked above

import {
  exportToCanvas as _exportToCanvas,
  exportToSvg as _exportToSvg,
} from "../scene/export";

Probably it could be related to #546 so my guess is when I am using the mocked module in some other file, it just goes in to a recursion loop and hangs the tests.

I have also tried doMock, importActual, hoisted and none of them work.
Any help would really be appreciated.
Thank you!

Reproduction

its the same issue mentioned above and reproducible in my PR excalidraw/excalidraw#6713

This is the file where I am trying to mock it https://github.com/excalidraw/excalidraw/blob/master/src/tests/packages/utils.test.ts#L6

Unfortunately the codesandbox integration with repo isn't working rn so I am not able to attach the link here, as soon as thats fixed, I can link here as well.
If there is any info which you need please let me know

System Info

#

Used Package Manager

yarn

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.

[ad1992]

After debugging and trying out various approaches I am using spy + mockImplementation to achieve the same and thats working for now

[sheremet-va]

This was fixed some time ago (cannot find PR) and should work correctly in the latest Vitest version.