`uvu` is not browser compatible

Not sure if this is intentional and there’s just a note missing in the README, but uvu/assert relies on kleur, which assumes process exists.

I’d love if I could just bundle my test suite and run it in the browser.

[lukeed]

Oh gotcha.

uvu will always just be the core test runner & “write the tests”-collection of utilities. It will remain agnostic to its environment, but always work as a Nodejs test runner by default.

umu will be the opinionated browser orchestration tool. Like uvu, it will have its own CLI but could also be used programmatically. It’s basically a wrapper around playwright (might make this flexible) and take care of the 90% use case of what people want from a frontend-testing setup. It will also have a programmatic interface so that you could pull it into existing tests or control tabs/page-reloads/etc if desired. The idea here is that you don’t like or want the done-for-you solution (umu), you can always build on top of uvu, since it should be flexible & light enough to do what you want to do.

TBH I’m not working on any frontend codebases right now, which means I’m not working on umu right now either, haha.

Until then, you could import puppeteer/playwright directly into your uvu tests & do what you need to do – including collecting coverage. There are examples of this in the repo already & there are a number of projects that are using this approach w/ uvu too.

So ya, uvu itself is nearly done, but its roadmap is:

• parallel suite execution (done)
• describe-style api (easy)
• improved programmatic api/experience
• remaining diff’ing TODOs
• timeout control (maybe)
• esm loader hook (future)
• global hooks (maybe)
• grep (maybe)

[gautelo]

This is the first I heard about an umu package. I found it on the npm registry (https://www.npmjs.com/package/umu), but it’s link to github is dead. Was the project cancelled or did it just get moved somewhere else, getting a new name or something like that?