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

@exactjs/bun-test

v0.7.1

Published

Bun test runner integration, DOM setup, compiler preload, and matchers for eXact

Readme

@exactjs/bun-test

Bun test-runner integration for eXact applications.

Setup

Add the preload to bunfig.toml:

[test]
preload = ["@exactjs/bun-test/preload"]

Then import component-testing APIs from @exactjs/bun-test. The preload registers the eXact Bun compiler plugin, installs Happy DOM when browser globals are absent, and adds the shared eXact matchers to Bun's expect.

Run the suite with Bun's browser export condition so DOM-facing framework packages select their compiled client artifacts:

{
	"scripts": {
		"test": "bun --conditions=browser test"
	}
}

The preload cannot change export conditions for modules Bun resolves before executing it, so the condition belongs on the Bun process rather than in preload code.

Use configureExactBunTest() for a custom preload, or import @exactjs/bun-test/setup when compilation and DOM setup are handled elsewhere. To define components inside test files, use a custom preload that calls configureExactBunTest({ compiler: { compileTestModules: true } }) instead of the default preload. The compiler prepares native definitions in .test, .spec, and .jest TSX modules while Bun owns test registration.

Documentation | Source on GitHub

For a paired SSR test, keep JSX render helpers in a fixture module that imports a generated .exact.server.js artifact. Helper modules with server-owned exports and no component definitions or client-owned exports receive the server projection. Client component fixtures in the same suite retain their client projection. Separate mixed component/helper modules or select their target explicitly.