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

@vex-chat/types

v2.0.0

Published

Wire protocol types for the Vex encrypted chat platform

Readme

@vex-chat/types

npm CI Released License Types Type Coverage Node Bundle OpenSSF Scorecard Socket

Wire protocol types for the Vex encrypted chat platform. Used by both the server and client so they speak the same shapes.

What's in the box

  • TypeScript interfaces for every REST payload, WebSocket message, and database record on the wire.
  • Zod 4 schemas (XSchema) paired with every interface for runtime validation: UserSchema.parse(data), KeyBundleSchema.safeParse(data), etc.
  • OpenAPI 3.1 document generated from the Zod schemas, shipped as a subpath export (@vex-chat/types/openapi.json). 16 REST paths.
  • AsyncAPI 3.0 document for the WebSocket protocol, also a subpath export (@vex-chat/types/asyncapi.json). 11 message types across 5 client→server and 6 server→client channels.
  • Discriminated WSMessage union so switch (msg.type) narrows exhaustively in TypeScript.

Install

npm install @vex-chat/types

zod is a required runtime dependency (auto-installed). No peer dependencies.

Usage

import { UserSchema, type User } from "@vex-chat/types";

// Compile-time: plain TypeScript interface
const alice: User = {
    userID: "a-uuid",
    username: "alice",
    lastSeen: new Date().toISOString(),
};

// Runtime: validate untrusted input from the wire
const parsed = UserSchema.parse(incomingJson); // throws on mismatch
const safe = UserSchema.safeParse(incomingJson); // { success, data } | { success, error }

For the REST/WS protocol docs:

import openapi from "@vex-chat/types/openapi.json" with { type: "json" };
import asyncapi from "@vex-chat/types/asyncapi.json" with { type: "json" };

License

AGPL-3.0-or-later