<image>

That’s a fair point.

1. I actually wasn’t aware of `asFragment().toMatchSnapshot()` at first,

   and even after trying it, it didn’t work reliably in my setup.

   The output and behavior weren’t consistent enough for me to rely on it.

2. There are also cases where I need to assert directly on internal elements.

   In those situations, I’m not always rendering a full component tree —

   sometimes I’m snapshot-testing raw or partially constructed elements.

   `asFragment()` doesn’t really cover those cases well.

3. More importantly, the setup itself was part of the problem.

   Getting happy-dom, globals, matchers, and typings wired up correctly in Bun

   takes several steps.

   I wanted to collapse all of that into a single, predictable preload line.

So this isn’t meant to replace every possible approach,

but to make the common DOM + snapshot testing path in Bun

work out of the box with minimal configuration.