@moq/net

The TypeScript twin of moq-net: connections, origins, broadcasts, tracks, groups, and frames, negotiating moq-lite or moq-transport at setup.

import * as Moq from "@moq/net";

const connection = await Moq.Connection.connect(new URL("https://cdn.moq.dev/anon?jwt=..."));

// Publish
const broadcast = new Moq.Broadcast.Producer();
connection.publish(Moq.Path.from("chat.room"), broadcast);
const track = broadcast.createTrack("messages");
const group = track.appendGroup();
group.writeString("hello");           // or writeFrame({ payload, timestamp })
group.close();

// Subscribe
const consumer = connection.consume(Moq.Path.from("chat.room")).track("messages").subscribe({ priority: 0 });
for (;;) {
    const group = await consumer.recvGroup();
    if (!group) break;
    console.log(await group.readString());
}

• Connections race WebTransport against WebSocket and expose a closed promise. Connection.Reload reconnects with backoff and re-publishes, which the elements use.
• Discovery by prefix (connection.announced(prefix)), and on-demand serving when a requested track or broadcast doesn't exist yet.
• Subscriptions carry a priority and latency budget; groups arrive out of order and are read frame by frame, with Lagged when frames were evicted before you read them.
• Datagrams on moq-lite 05+ and fetch-by-sequence for history.
• Remote errors carry the peer's reset code (RemoteError), the same on either transport.
• Paths with Path.relative for the cross-broadcast catalog references hang uses.

Examples in js/net/examples/. Runs in the browser and, over WebSocket, in Node, Bun, and Deno; see server-side.