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-plugin

v0.7.1

Published

Bun build integration for eXact TypeScript and TSX.

Readme

@exactjs/bun-plugin

Bun build integration for eXact TypeScript and TSX.

Configuration

Configuration discovery and authorization follow Bun's build root (otherwise the process directory). Override with applicationRoot.

import { exact } from '@exactjs/bun-plugin';

const exactPlugin = exact({ target: 'client' });
try {
	const result = await Bun.build({
		entrypoints: ['./src/client.tsx'],
		outdir: './dist',
		target: 'browser',
		format: 'esm',
		splitting: true,
		plugins: [exactPlugin]
	});
} finally {
	await exactPlugin.dispose();
}

When the eXact configuration declares microfrontend exposures, use the asynchronous coordinator so the artifact plan can add its entrypoints before Bun.build begins:

import { exactBuild } from '@exactjs/bun-plugin';

await exactBuild({
	entrypoints: ['./src/client.tsx'],
	outdir: './dist',
	target: 'browser',
	format: 'esm',
	splitting: true
});

exactBuild() installs exact() automatically. It emits actual exposure entry URLs through onRemoteEntries only after a complete successful generation and offers stable development IDs through onRemoteDevelopmentEntries. Direct Bun.build({ plugins: [exact()] }) remains supported for ordinary builds and reports an actionable error if exposures require the coordinator. Nonempty publicPath prefixes such as /assets are normalized to /assets/ for linked chunks; use the published entry map instead of predicting generated filenames. exactBuild() always releases its compiler resources after the build settles. A host that installs exact() directly must retain the plugin and call its idempotent dispose() after the final build or watch generation, including when Bun.build() rejects.

Use target: 'server' with Bun's server target for the matching server build. Keep serverComponents, React compatibility, and build identity consistent across paired outputs. For browser builds, set renderMode: 'hydrate' when the entry adopts SSR HTML or renderMode: 'client' when it only performs fresh mounts. The default universal contract remains available when one output must support either mode. For an SSR-only server entry, set renderMode: 'server-render' to omit continuation-dispatch executors. Keep the default for a Bun server bundle that also handles continuation requests.

The plugin compiles eXact source, resolves generated .exact facades, selects client or server exports, and participates in Bun watch builds. Use @exactjs/bun-adapter separately to connect the generated server runtime to Bun.serve().

Server builds authorize compiler-reached component packages before their onLoad hooks run and write private authorization and audit manifests under .exact/. Configure the shared policy with componentLibraries in exact.config.*. Bun server --hot is rejected because Bun cannot yet preserve a last-valid authorization generation; use watch builds instead.

Attributed enhancement imports populate the application-bundle enhancement catalog. The plugin redirects DOM, hydration, and SSR entry points through the shared facades that supply that catalog; the compiler does not decide package trust or maintain a plugin registry. An attributed namespace export with scope: 'package' in exact.config.* supplies a virtual namespace to every package component; Bun emits its catalog registration only from modules that activate it.

Optional debug settings control private server catalogs and browser instrumentation. Disable both for hardened output. See eXact DevTools. Shared .ts and .js helpers support pending state. See the task reference for receiver limits.

Policy conflicts warn at build and reject execution. Correct the policy and rebuild before deployment.

Documentation | Source on GitHub