Support jest-like `moduleNameMapper` in vitest

Clear and concise description of the problem

Sometime we have to deal with non-standard third-party packages, such as replace xxx/es/ to xxx/lib which are no need in “vite dev / build” so that CANNOT set with resolve.alias but ONLY need in testing phase, and it’s also NOT satisfy vitest deps.fallbackCJS mode.

Suggested solution

Maybe support some configuration like jest moduleNameMapper.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that request the same feature to avoid creating a duplicate.

[zthxxx]

Because of the time, I want to try some way to bypass the problem before they fixed and publish a new version.

I have tried to use deps.inline: true (with install jsdom fixed the error above) and also vitest.config.ts with resolve.alias, but nothing works.

With resolve.alias, the reason maybe vite use @rollup/plugin-alias which use @rollup/plugin-node-resolve cannot make alias for sub-dependencies with PNPM.

[sheremet-va]

@sheremet-va such as replace xxx/es/ to xxx/lib which are NO need in “vite dev / build” but ONLY need in testing phase

Use process.env.VITEST or mode === 'test' to distinguish between test and dev env.