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

ump-plugin-websocket

v0.0.1

Published

UMP WebSocket Plugin — DOM-style WebSocket(url, protocols) backed by each platform's native WebSocket

Readme

ump-plugin-websocket

DOM-style WebSocket(url, protocols) for UMP apps — RFC 6455 + WHATWG-shaped, backed by each platform's native WebSocket (OkHttp on Android, NSURLSessionWebSocketTask on iOS, @ohos.net.webSocket on HarmonyOS).

Install

npm install ump-plugin-websocket

Peer dependencies (must already be installed in your app):

  • ump-core
  • ump-native

Usage

import { WebSocket, CloseEvent } from 'ump-plugin-websocket';

const ws = new WebSocket('wss://example.com/echo', 'graphql-ws');

ws.addEventListener('open', () => ws.send('hello'));
ws.addEventListener('message', (ev) => console.log('got', ev.data));
ws.addEventListener('close', (ev: CloseEvent) => {
  console.log('closed', ev.code, ev.reason, ev.wasClean);
});
ws.addEventListener('error', () => console.log('error'));

// Binary frames — Uint8Array or ArrayBuffer
ws.binaryType = 'arraybuffer';
ws.send(new Uint8Array([1, 2, 3, 4]));

// Application-level close codes (1000 or 3000-4999)
ws.close(3999, 'app-level reason');

Importing this module also installs globalThis.WebSocket and globalThis.CloseEvent when the host doesn't already provide them, so libraries that look up the bare global names (RxJS, graphql-ws, MQTT, EventSource fallbacks) just work.

API surface

DOM WebSocket interface honoured:

| Member | Notes | |-------------------------------------------|--------------------------------------------------------| | new WebSocket(url, protocols?) | protocols may be string or string[] | | Static + instance CONNECTING/OPEN/CLOSING/CLOSED | 0/1/2/3 | | url, protocol, readyState | protocol reflects what the server selected | | bufferedAmount | Always 0 (deferred to v2 — see source comments) | | binaryType | 'blob' (default) or 'arraybuffer'. 'blob' falls back to ArrayBuffer delivery (Hermes ships no Blob). | | onopen / onmessage / onerror / onclose | Property setters | | addEventListener / removeEventListener | 'open' \| 'message' \| 'error' \| 'close' | | send(data) | Accepts string, ArrayBuffer, ArrayBufferView (Uint8Array). No Blob. | | close(code?, reason?) | Code must be 1000 or in [3000, 4999]; reason ≤123 UTF-8 bytes |

Close events

CloseEvent exposes code, reason, and wasClean per spec.

Migration from ump-native

In ump-native 0.1.x, WebSocket and CloseEvent were bundled with the main package. Starting 0.2.x, they ship as this separate plugin.

- import { WebSocket, CloseEvent } from 'ump-native';
+ import { WebSocket, CloseEvent } from 'ump-plugin-websocket';

The global install side-effect (globalThis.WebSocket) still fires on import, so existing code that relies on the bare global continues to work — just import this plugin once at app boot.

No API changes.