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

@pepys/testing

v0.4.0

Published

Test a pepys plug-in on Bun: an in-memory store that runs its consumers and queries

Readme

Test a pepys plug-in on Bun, with no host and no network.

The test store runs a plug-in's consumers over one in-memory database, with every table, the link table and the shared views, and answers the plug-in's queries. It repeats the host's link check and scope replace in TypeScript. It does not prove the scriptc compile or the Rust host.

Install

bun add -d @pepys/testing

Set the compiler options from the kit's README.

Then apply facts, and test a query on the rows that the plug-in's consumers write from them. A query test that seeds through the consumers fails when a consumer changes the shape of its rows:

import { expect, test } from 'bun:test';
import { createTestStore } from '@pepys/testing';
import { shelfPlugin, shelfSource, shelfTitleQuery } from './shelf-plugin.ts';

test('it answers a query from the row that a shelved fact gives', async () => {
  await using store = await createTestStore({ plugins: [shelfPlugin] });

  await store.apply(shelfSource, [
    {
      type: 'shelf.book.shelved',
      event: 'evt-1',
      entity: 'shelf:book:atlas',
      at: '2026-11-01T08:00:00.000Z',
      payload: { title: 'The Coral Atlas' },
    },
  ]);

  const answer = await store.query(shelfTitleQuery, { id: 'shelf:book:atlas' });

  expect(answer).toStrictEqual({ title: 'The Coral Atlas' });
});
bun test

Features

  • createTestStore: apply facts or write rows, then run a query, read rows and read links.
  • applyFactLog: apply the facts that createIngest of @pepys/ingest stored in a memory fact log to a test store, in place of the host. A second call applies only the records the log stored after the first.
  • applyInBothOrders: apply facts in two orders and compare the stores.
  • The memory adapter of the store reader, for a test of a core query.

Documentation

The pepys docs hold the design of the test store.