Tests not found when using in-source testing and browser mode

[jtmthf]

Describe the bug

When using in-source testing and browser mode together, tests fail with the error of "No test suite found in file". With an external file, the tests are found and succeed. When browser mode is disabled, the tests are found but fail due to relying on browser features. Below is the test source.

if (import.meta.vitest) {
  const { test, expect } = import.meta.vitest;

  test("button click updates count", async () => {
    const { act, render, screen } = await import("@testing-library/react");
    const { userEvent } = await import("@vitest/browser/context");

    render(<App />);

    const button = screen.getByRole("button");

    await act(async () => {
      await userEvent.click(button);
    });

    expect(button).toHaveTextContent("count is 1");
  });
}

Reproduction

https://github.com/jtmthf/vitest-in-source-browser

System Info

System:
    OS: macOS 14.6.1
    CPU: (8) arm64 Apple M2
    Memory: 80.78 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.local/state/fnm_multishells/98308_1725115559526/bin/node
    Yarn: 1.22.19 - ~/.local/state/fnm_multishells/98308_1725115559526/bin/yarn
    npm: 10.2.3 - ~/.local/state/fnm_multishells/98308_1725115559526/bin/npm
    pnpm: 9.4.0 - ~/.local/state/fnm_multishells/98308_1725115559526/bin/pnpm
  Browsers:
    Chrome: 128.0.6613.86
    Chrome Canary: 106.0.5249.3
    Safari: 17.6
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1 
    @vitest/browser: ^2.0.5 => 2.0.5 
    vite: ^5.4.1 => 5.4.2 
    vitest: ^2.0.5 => 2.0.5

Used Package Manager

pnpm

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.