feat: init @vitest/browser package

[antfu]

Rework #891

Checklist

• Init package and integration
• Stub node packages for Vitest runtime (in progress, encounter some bug)
• Fulfill tests (Browser only APIs, Vue and React components)
• Better log in terminal
• Show progress and error on the browser page
• Headless mode in CI
• Docs

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	2e40c87
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/62d1c8ebcdd006000a45ec71
😎 Deploy Preview	https://deploy-preview-1302--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[userquin]

@antfu the ui at least loading on the browser, and also the tests are loaded, but we have some problem with node:util package to format messages, I haven't found a way to bypass it, see screenshots below.

My commit also includes:

• added root script to copy ui to browser dist on root build script
• changes some config.web to config.browser (unresolved conversation)
• changed vitest to vitest/browser on browser node module on /__vitest_index__ request, it was loading vitest instead the browser module
• added isNode, isBrowser and config.browser logic to vitest modules to avoid run tests on server (fails)

[userquin]

Can we add a delay in the browser ui to solve it? I will check it later.

EDIT: I will add an WS ping/pong to add the ui package in the browser ui

resolved

[cristian-spiescu]

Hi there! We have library that enriches the react-testing-library dev/test workflow, with visual features. We are "polishing" this lib, and we'd like to release it as open source. We currently use mocha. We are interested to use Jest/Jest compatible also, because this would fit the programming habits of more people (compared to our current setup).

That's why I find vitest-browser really interesting. Could you please share your plans/roadmap regarding this feature?

[Aslemammad]

@cristian-spiescu Hey mate, Lately I've been talking to @userquin @JessicaSachs! and here's my plan:

• Implement CI compatibility
• Bring Proper selectors
• More stable environment