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

@pingpal/protocol

v0.1.2

Published

Shared wire protocol for PingPal — zod schemas, types, 90-char validation, and NDJSON framing.

Readme

@pingpal/protocol

The shared wire protocol for PingPal. Every other package depends on this one, and it depends on nothing but zod — so it stays tiny and fast to test.

It defines the messages that travel over both transports: the WebSocket link to the relay and the local Unix-socket IPC between the daemon and its clients.

What's in here

  • Zod schemas + types for every envelope: hello, presence, ping, ack, and error. Parsing and type are derived from the same schema, so the validator and the TypeScript type can never drift apart.
  • The 90-char rule. MAX_PING_CHARS = 90 and validatePingText(text) (returns a PingTextResult) are the single source of truth for the cap. The ping schema enforces it too, so an over-long ping cannot pass validation anywhere — client, relay, or IPC.
  • NDJSON framing. Newline-delimited JSON helpers used by both the relay socket and the IPC socket: encode an envelope to a line, and decode a byte stream into envelopes (handling partial frames).
  • newId() for stable, collision-resistant ping ids.
  • PROTOCOL_VERSION so peers can detect a version skew.

Usage

import { PingSchema, validatePingText, MAX_PING_CHARS } from "@pingpal/protocol";

const result = validatePingText(text);
if (!result.ok) throw new Error(`ping too long (max ${MAX_PING_CHARS})`);

const ping = PingSchema.parse({ id, from, to: null, text, ts });

Development

pnpm --filter @pingpal/protocol build
pnpm --filter @pingpal/protocol test   # schemas, the 90-char boundary, framing round-trips