Modules with alias are not mocked

[BrevAlessio]

Describe the bug

If I try to mock a module imported by another module, by providing an alias as key, such as vi.mock('@module-alias'), the module is not mocked as expected.
If I provide the relative path as key, such as vi.mock('..src/MyModule'), the module is mocked as expected.

// MyInnerModule
export const MyInnerModule = { key: undefined }

// MyModule
import { MyInnerModule } from '@/MyInnerModule'
export const MyModule = { key: MyInnerModule.key }

// MyModule.test
import { MyModule } from '@/MyModule';
import { vi, describe, it, expect } from 'vitest';

// Try with relative path ../src/MyInnerModule, it works
vi.mock('@/MyInnerModule', () => {
  return {
    MyInnerModule: {
      key: 1,
    },
  };
});

describe('MyModule', () => {
  it('should have key', () => {
    expect.assertions(1);
    expect(MyModule.key).toBe(1); // Got undefined
  });
});

This issue may be related to #2777 but it didn't solve my case.

Reproduction

Stackblitz, follow the instruction on line 4 to switch between non working and working
https://stackblitz.com/edit/vitest-dev-vitest-qj31uc?file=test/MyModule.test.ts

System Info

All the infos are on stackblitz:

  "devDependencies": {
    "@vitest/ui": "latest",
    "vite": "latest",
    "vitest": "0.29.8"
  },

Used Package Manager

npm

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.

[sheremet-va]

Don't use relative paths in aliases: https://vitejs.dev/config/shared-options.html#resolve-alias

[BrevAlessio]

Sorry, my bad, I totally missed that.