Vitest UI doesn't render tests initially

[rothsandro]

Describe the bug

Starting Vitest with the --ui parameter will open the Vitest UI and run all tests, but the UI doesn't show any tests. I have to reload the UI in the browser to see the tests. This only happens after updating to Vitest UI 2.x

Reproduction

Can be reproduced with the StackBlitz demo you provide: https://stackblitz.com/edit/vitest-dev-vitest-q9metk?file=README.md&initialPath=__vitest__/

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: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 2.0.1 
    vite: latest => 5.3.3 
    vitest: latest => 2.0.1

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.

[userquin]

The ui is faster than server logic, we need to include files if not loaded on initial ws connection: https://github.com/userquin/vitest-issue-6065 (added some logs and sourcemap for local tgz vitest ui)

[devbucket]

Maybe it's only me, but I do not understand this answer.
I am facing the same issue, as the UI is not showing any tests. Only when refreshing the browser, does it. But still, then it does not automatically update when the tests are still running.

[sheremet-va]

Maybe it's only me, but I do not understand this answer.

I am facing the same issue, as the UI is not showing any tests. Only when refreshing the browser, does it. But still, then it does not automatically update when the tests are still running.

This is a bug. Expect a fix in the next version