Add support for vitest browser tests

[smcenlly]

As per the title, this issue is to add support for vitest browser tests

[smcenlly]

Vitest browser mode is currently experimental with specific notes:

This feature is currently under development, and APIs may change in the future.

The browser mode feature of Vitest is still in its early stages of development. As such, it may not yet be fully optimized, and there may be some bugs or issues that have not yet been ironed out. It is recommended that users augment their Vitest browser experience with a standalone browser-side test runner like WebdriverIO, Cypress or Playwright.

---

This feature request is on hold until the experimental flag is removed, or the APIs are guaranteed to not change.

[pawk3k]

@smcenlly just want to appreciate the work you did with Wallaby.js , gamechanger for me <3

[spookyuser]

I've been loving the browser mode in vitest for chrome extensions but noticed that in the intro to wallaby the page says:

By default wallaby.js uses Google Chrome (headless) to run tests. If you want to use wallaby.js to run your node.js tests, or run your tests in the latest Chromium/V8 via Electron, or run your tests in PhantomJs, you will also need to specify the env configuration property.

Does this mean that by default wallaby is kind of doing what vitest's browser mode is doing anyway?

[smcenlly]

Does this mean that by default wallaby is kind of doing what vitest's browser mode is doing anyway?

If you are using Wallaby with Chrome, then you need to use one of the testing frameworks that we support for running in the browser. Refer to our docs here.