Browser: Simple TypeScript test appearing+running in CLI mode but not Browser mode

[frank-weindel]

Describe the bug

I have a simple TypeScript project with a single test file. The test file has only one test. When I run vitest in normal CLI mode the test is successfully run. When I run vitest --browser "chrome" the browser and vitest UI are launched but no tests are run.

Reproduction

https://github.com/frank-weindel/vitest-3286-browser-typescript

• npm install
• Run npm start to see example app working.
  • You should see "1 + 1 = 2" in browser
• Run npm run test to see test for add() method running successfully
• Run npm run test:browser to see Chrome browser + Vitest UI launching but no tests are run.

System Info

System:
    OS: macOS 12.2.1
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.14.0 - ~/.nodenv/versions/16.14.0/bin/node
    npm: 8.3.1 - ~/.nodenv/versions/16.14.0/bin/npm
  Browsers:
    Chrome: 112.0.5615.137

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.

[tpluscode]

I think I have the same problem. The browser window opens but the network shows a hanging request for http://localhost:63315/@id/vitest/utils

[frank-weindel]

@tpluscode I actually had that problem originally. But I found a workaround. See #3124 (comment).

[tpluscode]

Thanks!

[tpluscode]

Now the vitest UI loads but I get 504 Outdated Optimize Dep for the request for http://localhost:63315/@id/vitest/browser

[tpluscode]

By experimenting blindly with the opimizeDeps options, I found that the 504 response is solved by setting noDiscovery: true

Then however, I sometimes get an error like:

SyntaxError: The requested module '/node_modules/concordance/index.js?v=ea45bb1f' does not provide an export named 'default'

[userquin]

Should be fixed in next 0.31.0 release, check optimizeDeps in #3190 (you need to remove .vite folder)

[abrowne2]

This is similar to my experience; removing the .vite folder does not seem to fix the issue either.

If I run vitest --ui my simple typescript tests are identified and pass, but if I run vitest --browser, with the same tests present, they show as No test suite found in file.

Using vitest 0.33.0

[sheremet-va]

This should be fixed now.