npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@zgeoff/bun-test-react

v0.2.3

Published

bun test preloads for React client code: happy-dom with Bun's fetch stack, jest-dom matchers, and per-test unmount and zustand reset

Readme

@zgeoff/bun-test-react

bun test preloads for React client code: a happy-dom document that keeps Bun's own fetch stack, the jest-dom matchers, and a clean slate after each test — every rendered tree unmounted, then every zustand store back at its initial state.

Usage

bun add -d @zgeoff/bun-test-react @testing-library/react react react-dom
# bunfig.toml — order matters: the zustand preload must wrap `createStore` before any store exists
[test]
preload = ["@zgeoff/bun-test-extended", "@zgeoff/bun-test-react/zustand", "@zgeoff/bun-test-react"]
// tsconfig.json — loads the jest-dom matcher types; the DOM libs come from @zgeoff/tsconfig/react.json
{ "compilerOptions": { "types": ["bun", "@zgeoff/bun-test-extended", "@zgeoff/bun-test-react"] } }

Leave out the zustand preload in a repo without zustand.

The preload registers happy-dom with its default settings, so a test document fetches no external stylesheet and loads no iframe page.

Why each piece is there

  • happy-dom replaces the fetch globals with its own, and Bun's ReadableStream.pipeTo and fetch reject them. The preload restores Bun's fetch stack after registering happy-dom.
  • @testing-library/dom binds screen to the document it finds when it loads, so the preload loads jest-dom and @testing-library/react only after happy-dom exists.
  • A failing matcher prints a DOM node as its opening tag, not as happy-dom's whole object graph.
  • Trees unmount before the store reset: a reset under a mounted tree re-renders it, and its effects write the old test's state back.