happy-dom VS solid-primitives

Next we’ll install Vitest and happy-dom to the project by running:

JSDOM and happy-dom for DOM and browser API mocking

https://github.com/capricorn86/happy-dom/issues/618. Looks like some work was merged recently.

I think you mean jsdom. You can try Happy DOM

Well, I've actually done it using axios + happy-dom.

You may have heard of vite, the slim fast dev server that scored an amazing as deserved 98% satisfaction on the state of js survey 2021. It's creators found unit testing too cumbersome and slow and decided to add their own perspective to the task. The result is vitest: it runs a vite server under the hood to transform the code to test as fast as possible, uses an enhanced flavor of chai to have jest-compatible assertions, integrates DOM mocking using jsdom or happy-dom and even the tiny-spy library that was just built as a separate library to allow for easy reuse is small and compatible with jest.

happy-dom, more lightweight

Solid.js is already pretty powerful, but even so, there are things it cannot do out of the box. Here's where the community comes in and provides packages to enhance your development experience: solid-primitives.

As for component libraries, I also just don't like or use them anymore. I find that they just get in my way. What I really like is the community primitive packages that solve all the lower level challenges when building certain types of components. I personally find that to be enough.

Check out Solid primitives.

This might be helpful: https://github.com/solidjs-community/solid-primitives/tree/main/packages/event-bus

So you can have a look at the test in the solid-primitives repository.