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

@moq/qmux

v0.3.3

Published

QMux protocol (draft-ietf-quic-qmux-02) over WebSockets

Readme

@moq/qmux

A WebTransport implementation using WebSockets as the underlying transport with QMux (draft-ietf-quic-qmux-02, negotiating down to draft-01 and draft-00) framing: a polyfill in browsers, and a server on any runtime that can accept a WebSocket.

QMux brings QUIC's multiplexed streams and flow control to reliable, ordered byte-stream transports like WebSockets. This allows WebTransport applications to seamlessly fall back when QUIC/UDP is blocked by network middleboxes.

Install

npm install @moq/qmux

Usage

Use as a drop-in WebTransport replacement:

import Session from "@moq/qmux"

const transport = new Session("https://example.com/endpoint")
await transport.ready

const stream = await transport.createBidirectionalStream()

Servers

Session.accept runs the other role, over a WebSocket your server has already accepted. The host performs the upgrade, so it — not this library — chooses the subprotocol; selectSubprotocol picks the value to accept from what the client offered, and the session reads the wire-format version back off the socket.

import Session, { selectSubprotocol } from "@moq/qmux"

Deno.serve((req) => {
	const protocol = selectSubprotocol(req.headers.get("sec-websocket-protocol"), {
		protocols: ["moq-lite-04"],
		versions: { "moq-lite-04": null },
	})
	if (!protocol) return new Response("no supported protocol", { status: 400 })

	const { socket, response } = Deno.upgradeWebSocket(req, { protocol })
	const session = Session.accept(socket)
	handle(session) // a WebTransport, same as the client side
	return response
})

Any already-accepted WebSocket works — Deno.upgradeWebSocket, Node's ws, or a WebSocketStream. Accepting the upgrade without a negotiated subprotocol falls back to the legacy webtransport wire format, so reject the request when selectSubprotocol returns undefined rather than accepting a socket the peer's framing won't match. If your host doesn't expose the negotiated value on the socket, pass it explicitly as { protocol }.

The result is an ordinary WebTransport: the only difference from a client session is which half of the stream-id space each side owns.

Detecting a dropped session

closed follows the WebTransport contract:

  • Fulfills with { closeCode, reason } on a graceful end: either side called close(), which puts an APPLICATION_CLOSE (0x1d) on the wire.
  • Rejects on an abnormal end: a CONNECTION_CLOSE (0x1c) arrived — the transport variant a peer sends when it caught a protocol violation — or no close frame arrived at all, because the socket dropped or the peer went idle. This endpoint rejects the same way when it catches the peer violating the protocol, and sends a CONNECTION_CLOSE so the peer rejects too.
try {
	const info = await transport.closed
	console.log("closed gracefully", info.closeCode, info.reason)
} catch (err) {
	// err is a WebTransportError-shaped SessionError: err.source === "session"
	console.warn("session dropped, reconnecting", err)
}

Don't reach for closeCode to tell the two apart — close codes are application-defined, so a graceful close may carry any value, including one that looks like a violation, and an app closing with 1006 is indistinguishable from a dropped socket. Which frame arrived is the signal, and the settled state is how you read it.

Stream reset codes

A reset carries an application error code in both directions, like native WebTransport:

import { StreamError } from "@moq/qmux"

// Send RESET_STREAM with code 26.
await stream.writable.abort(new StreamError(26))

// Receive one: the code is a field, not text buried in the message.
try {
	await reader.read()
} catch (err) {
	// err.source === "stream"
	console.warn("reset by peer with code", err.streamErrorCode)
}

The outgoing code comes off the reason passed to abort() / cancel(), so any WebTransportError (native or the exported StreamError) sends its streamErrorCode and anything else sends 0. STOP_SENDING works the same way, erroring the sender's writable with the code the peer chose.

Polyfill

Install as a global WebTransport polyfill:

import { install } from "@moq/qmux"

// Only installs if native WebTransport is unavailable
install()

// Now use the standard WebTransport API
const transport = new WebTransport("https://example.com/endpoint")

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.