__mocks__ folder doesn't work

[fadi-george]

Describe the bug

__mocks__ is a common way (with Jest) to mock node-modules (and something helpers). But currently it doesn't seem to work. It works for my regular Jest setup that uses vite-tsconfig-paths.

Reproduction

https://stackblitz.com/edit/node-b3r6jj?file=src%2FSomeComponent.spec.tsx

I tried vite-tsconfig-paths (similar to my own setup), as well as Vite's own resolve alias config. Neither work.

System Info

System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 82.06 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Brave Browser: 97.1.34.80
    Chrome: 97.0.4692.71
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-react: ^1.1.4 => 1.1.4 
    vite: 2.7.12 => 2.7.12 
    vitest: 0.1.17 => 0.1.16

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]

We don't support automocking. You need to manually call vi.mock("path"). Or you can call it once in setupFiles.

For external libraries we use root/__mocks__ folder. For internal, you need to have __mocks__ folder inside the folder where the file is located.

Docs: https://vitest.dev/api/#vi-mock

Working stackblitz: https://stackblitz.com/edit/node-e1vryb?file=src/hooks/__mocks__/index.ts

[sschneider-ihre-pvs]

What about paths like @composable/useSomething will that be resolved in vi.mock ?

[sheremet-va]

What about paths like @composable/useSomething will that be resolved in vi.mock ?

yes

[sschneider-ihre-pvs]

Ok, that doesn't work also :)
is there a debugging possibility to inspect where vi.mock('@composable/useSomething') is looking for the mock?
seems like that kind of aliasing doesn't work so well with vite/vitest

[sheremet-va]

No debugging option available at the moment. You can look into examples/mocks in the repo.

If nothing works, please create an issue with reproduction.

[sschneider-ihre-pvs]

I tried it out in the stackblitz repo