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

@sr-receipts/host

v0.4.0

Published

The Mac-facing half of sr-receipts: the reader interface a test uses, the wire to a guest daemon, and NVDA as a session over it.

Readme

@sr-receipts/host

The Mac's side of sr-receipts: the reader interface a test uses, the wire to a guest daemon, and NVDA as a session over that wire.

Ownership

This package owns:

  • ReaderSession in src/protocol.ts: the one interface a test sees for either reader, with Guidepup's method names
  • the wire protocol, also in src/protocol.ts: the daemon's routes and their bodies, and PROTOCOL_VERSION, bumped by hand when either changes shape
  • createReaderSession in src/session.ts: the Reader Session every reader is built with. It wraps a reader adapter and owns the transcript, the serialization of calls, the rule that every call rejects rather than throws, the restart on start and the stop that never throws
  • createNvdaSession, NVDA's adapter over the daemon's routes

It does not know how any screen reader is driven, and it depends on nothing but Node's fetch. @sr-receipts/daemon implements the protocol and depends on this package for it. A change to src/protocol.ts is a change to both packages and belongs in both changelogs. A change to the routes or their bodies also bumps PROTOCOL_VERSION: the daemon reports the version it was built against in /health, and createNvdaSession's start refuses a daemon reporting another, naming both, because the Mac and the guest are installed at different times.

Use

Most consumers reach this through the reader fixture in @sr-receipts/playwright. Directly:

import { createNvdaSession } from "@sr-receipts/host";

const nvda = createNvdaSession({ url: process.env.RIG_URL, token: process.env.RIG_TOKEN });
await nvda.start();
await nvda.enter(page);                        // a Playwright page, or anything with title(), bringToFront(), evaluate()
const { spoken } = await nvda.capture(() => page.getByRole("checkbox").first().click());
console.log(spoken, await nvda.next());
await nvda.stop();
console.log(nvda.transcript.join("\n"));

enter throws with the guest's whole diagnosis when the guards fail. Every other call returns what the reader said, "" for silence, and the transcript names silence. A refused request is a RigError carrying the status; a reader failure on the guest arrives with its cause chain.

Versioning

Pre-1.0 semantic versioning: a minor version may break the contract, and says so in CHANGELOG.md. Released with the other three packages, always at the same version.

Tests

npm test

The Reader Session against a fake adapter. The NVDA session is tested against the real daemon in @sr-receipts/daemon's test/wire.test.ts, since the daemon can depend on this package and not the other way round.