globalSetup file cannot use tsconfig import paths in vitest 4

[danieldietzler]

Describe the bug

Hey, in Vitest 3 it was possible to import files from src/ in a globalSetup file and the tsconfig paths would get applied correctly. In Vitest 4 however that seemingly isn't the case anymore.
I am not sure if this is actually a bug or expected behavior, it certainly changed between Vitest 3 and Vitest 4 though.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-jjjjuuud?file=test%2Fsetup.ts

The tsconfig.json has

   "paths": {
      "src/*": ["./src/*"]
    }

however, using src/basic.js in the import does not work in the globalSetup file; ../src/basic.js does.

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 4.0.16 
    vite: latest => 7.3.1 
    vitest: latest => 4.0.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]

It's expected that tsconfig paths are not respected by default: https://vitest.dev/guide/common-errors.html#cannot-find-module-relative-path