fix: normalize moduleCache path

[PatrickChen928]

fix: #1714

This problem is caused by the moduleCache key is not same in setup file and the vue component.
In setup file, the key is /@fs/user/../node_modules/vue-meta/dist/vue-meta.cjs.js, but in the component, is /node_modules/vue-meta/dist/vue-meta.cjs.js.

I'm not sure if this solution is the best, if not, modifications or rewrites are welcome~

[sheremet-va]

Can you add a test for this?

[PatrickChen928]

Can you add a test for this?

ok. I will do it later.

[jagoncalves14]

Thanks for this @ChpShy.
I applied your change directly in my node_modules/vitest folder to see if it fixes it — and it did! 👏

[PatrickChen928]

I'm confused that I can't reproduce this in vitest test. Maybe someone more familiar with vite and vitest could help with add test? Or I need more time to reproduce it.

[PatrickChen928]

It looks like it is caused by pnpm workspace, In workspace package, test success, because vue component also compiled to be /@fs/Users/xxx/node_modules/.pnpm/vue-meta@3.0.0-alpha.10_vue@3.2.37/node_modules/vue-meta/dist/vue-meta.cjs.js.

But in demo project, test failed, because vue component compiled to be /node_modules/.pnpm/vue-meta@3.0.0-alpha.10_vue@3.2.37/node_modules/vue-meta/dist/vue-meta.cjs.js.

And callFunctionMock is private, So, how can I add the test? @sheremet-va

[PatrickChen928]

Also, this maybe caused by vite. I'm not sure. Maybe someone can help to provide a reason? Hope for feedback~

[PatrickChen928]

because

I also test the different version of vite. It get the same result.

[sheremet-va]

So, how can I add the test?

You can add a unit test:

const mockMap = {
  ...your mocks
}
const mocker = new Mocker({ ...options })
const result = mocker.request(pathThatFailedBefore)

[PatrickChen928]

I think this had been solved by pr #1726

line: https://github.com/vitest-dev/vitest/blob/main/packages/vitest/src/runtime/mocker.ts#L298

Waiting for release~