In browser mode, aliases in the test section of vite.config are ignored

[dospunk]

Describe the bug

When using browser mode, aliases that are defined in the vite config's resolve.alias section work as expected but aliases defined in test.alias throw an error as if they are packages that have not been installed.

vite config example:

/// <reference types="vitest" />

import { defineConfig } from 'vite';
import { resolve } from 'path';

function pathResolve(dir: string) {
  return resolve(process.cwd(), '.', dir);
}

export default defineConfig({
  resolve: {
    // works
    alias: [{ find: /@src\//, replacement: pathResolve('src') + '/' }],
  },
  test: {
    browser: { enabled: true },
    // fails
    alias: [{ find: /@tests\//, replacement: pathResolve('test') + '/' }],
  },
});

output example:

Error: The following dependencies are imported but could not be resolved:

  @tests/testUtils (imported by path/to/the/test.ts)

Are they installed?

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-rb4nqu?file=vite.config.ts

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
    Memory: 7.92 GB / 15.78 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.15.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (111.0.1661.54)
    Internet Explorer: 11.0.19041.1202
  npmPackages:
    @vitest/browser: ^0.29.7 => 0.29.7
    @vitest/ui: latest => 0.29.7
    vite: latest => 4.2.1
    vitest: latest => 0.29.7

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.