MockNuxtImport huge module graph on vitest

[marcelobotega]

Hi,
We have a big project here using layers and an internal component library (150+ components). When we use the helper mockNuxtImport our module graph on vitest explode. We only mock two composables, but the module graph is huge, vitest ui struggles to render everything.

const { mockNavigateTo, mockUseRouter } = vi.hoisted(() => ({
  mockNavigateTo: vi.fn(),
  mockUseRouter: vi.fn(),
}));
mockNuxtImport('navigateTo', () => {
  return mockNavigateTo;
});

mockNuxtImport('useRouter', () => {
  return mockUseRouter;
});

If I change the mockNuxtImport to a vi.mock we have a smaller module graph.

const { mockNavigateTo, mockUseRouter } = vi.hoisted(() => ({
  mockNavigateTo: vi.fn(),
  mockUseRouter: vi.fn(),
}));

vi.mock('#app/composables/router', () => {
  return {
    navigateTo: mockNavigateTo,
    useRouter: mockUseRouter,
  };
});

My questions are:

• Is this an expected behavior of mockNuxtImport ?
• If not, what could be causing this huge module graph ?

Hope someone can help me with that.
Thanks.