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

@twilic/websocket

v0.3.0

Published

WebSocket helpers for Twilic binary frames.

Readme

@twilic/websocket

WebSocket helpers for Twilic binary frames.

Install

pnpm add @twilic/websocket @twilic/core

Usage

import { init } from "@twilic/core";
import { createTwilicWebSocket } from "@twilic/websocket";

await init();

const twilic = createTwilicWebSocket(new WebSocket("ws://localhost:8788"));

twilic.onMessage((value) => {
  console.log(value);
});

twilic.send({ id: 1n, name: "alice" });

One WebSocket message equals one Twilic frame. Send binary frames only (opcode 0x2).

Pass a browser WebSocket or a ws socket directly. In the browser, call init({ prefer: "wasm" }) from @twilic/core before using these helpers.

Stateful profile

One call binds one connection. That connection keeps its own outbound encoder and inbound decoder, and send() uses encodePatch():

import { init } from "@twilic/core";
import { createTwilicWebSocket } from "@twilic/websocket";

await init();

const twilic = createTwilicWebSocket(socket, {
  stateful: true,
  session: { maxBaseSnapshots: 8 },
});

twilic.onMessage((value) => {
  console.log(value);
});

twilic.send({ x: 100, y: 200, hp: 100 });
twilic.send({ x: 101, y: 200, hp: 100 });

Closing the socket ends the session. A new socket needs a new createTwilicWebSocket() call, and its first send() is a full frame.

API

  • TWILIC_CONTENT_TYPE
  • DEFAULT_MESSAGE_LIMIT
  • createTwilicWebSocket(socket, options?)
  • twilicSend(socket, value)
  • parseTwilicMessage(data, options?)
  • attachTwilicWebSocket(socket, listener, options?)
  • TwilicMessageLimitError
  • TwilicUnsupportedFrameError

twilicSend, parseTwilicMessage, and attachTwilicWebSocket are stateless one-shot helpers. Stateful traffic should go through createTwilicWebSocket(socket, { stateful: true }).

Runnable example

pnpm example:websocket          # server from twilic/examples
pnpm example:websocket:client   # client from twilic/examples

See websocket-session/.

Changelog

See docs/CHANGELOG.md.

License

This project is licensed under the MIT License - see the LICENSE file for details.