muxwsOne WebSocket, as many conversations as you need

Either end can start one. Any one of them can be cancelled on its own. A large payload never holds up a small one. It is the layer you would otherwise write again and again in every project.

Get Started

API Reference

GitHub

HTTP/2 and HTTP/3 semantics, on a WebSocket

The stream model HTTP/2 and HTTP/3 already settled - many independent streams, either end able to open one, cancellation per stream - without needing QUIC or an HTTP/3 stack.

Symmetric peers

One Peer type per language. Server push is the same mechanism as a client request.

Automatic fragmentation

Payloads above the 64 KiB frame constant are split and reassembled for you, with a round-robin writer.

Reconnect with hello replay

Jittered backoff, a heartbeat that bounds detection, and an opening payload replayed on every connection.

Pluggable codec

JSON by default, msgpack optional, your own if you want one - asserted at the handshake.

Ports, not bindings

Python and TypeScript today, each a full implementation of the same frozen wire. A third is a normative spec and 65 shared fixtures away - the corpus exists so nobody has to read either port's source to write one.