Start at v3.0, vitest does not correctly respect subpath imports.

[kongxiangyan]

Describe the bug

Start at v3.0, vitest does not correctly respect subpath imports, please check the minimal reproduction repo.

Reproduction

https://github.com/kongxiangyan-fork/subpath-imports-typescript

System Info

System:
    OS: Windows 11 10.0.26200
    CPU: (32) x64 AMD Ryzen 9 7945HX with Radeon Graphics        
    Memory: 52.89 GB / 95.20 GB
  Binaries:
    Node: 20.17.0 - C:\Users\kciga\AppData\Local\pnpm\node.EXE
    Yarn: 1.22.22 - C:\Users\kciga\AppData\Local\pnpm\yarn.CMD
    npm: 10.8.2 - C:\Users\kciga\AppData\Local\pnpm\npm.CMD
    pnpm: 9.9.0 - C:\Users\kciga\AppData\Local\pnpm\pnpm.EXE
    bun: 1.3.1 - C:\Users\kciga\.bun\bin\bun.EXE
  Browsers:
    Chrome: 143.0.7499.170
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11.0.26100.7309
  npmPackages:
    vite: ^7.2.6 => 7.3.0
    vitest: ^2.0.0 => 2.1.9

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.

[kongxiangyan]

I just noticed issue #9005. According to the instructions in that issue, the problem has already been resolved. However, I find the solution rather strange — ssr.resolve.conditions is so obscure that no one would think to look in that direction at first.

Perhaps you would consider adjusting it to a more general setting? For example:

{
  // currently `resolve.conditions`
  resolve.exports.conditions: string[],
  // currently `ssr.resolve.conditions`
  resolve.imports.conditions: string[],
}

[hi-ogawa]

resolve.conditions is for client application on Vite and resolve.ssr.conditions is for server application. This is a Vite's convention/feature, so Vitest is inheriting that. It might be worth mentioning it the doc if this connection is unclear.