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

@irbisadm/rtc-event-log

v0.1.0

Published

WebRTC RtcEventLog parser for JavaScript/TypeScript, ported from libwebrtc (WIP)

Readme

rtc-event-log

A parser for WebRTC RtcEventLog files (the logs Chrome writes from chrome://webrtc-internals and native libwebrtc clients produce via RtcEventLog) for JavaScript and TypeScript, ported from libwebrtc's logging/rtc_event_log.

Status: work in progress — the protobuf layer of the new log format decodes and the field encodings (varint, blob and delta encoding) are ported byte-exact; ParsedRtcEventLog parses every event type of the new format and of the legacy format (rtc_event_log.proto, raw RTP headers decoded with the logged header extension maps) and, like upstream, the few events of the v3 format that upstream parses (begin/end log, ALR state, audio playout, delay-based BWE updates), including the RTCP blocks (SR/RR, XR, REMB, NACK, PLI, FIR, BYE, loss notification, transport-wide and RFC 8888 congestion control feedback), and getPacketInfos() matches RTP packets with their feedback (see PORTING_PLAN.md).

Upstream revision

Ported from libwebrtc M154 — branch-heads/8037 @ 7cb44cfa. proto/rtc_event_log2.proto is copied verbatim from that revision; every ported file names its upstream source and revision in its first line.

Usage

import {readFileSync} from "node:fs";
import {ParsedRtcEventLog} from "@irbisadm/rtc-event-log";

const log = new ParsedRtcEventLog();
const status = log.parseString(readFileSync("event_log.rtc"));
if (!status.ok()) throw new Error(status.message());
for (const stream of log.outgoingRtpPacketsBySsrc()) {
  console.log(stream.ssrc, stream.outgoingPackets.length);
}

The API mirrors upstream ParsedRtcEventLog in camelCase. Times are Timestamps: microseconds as a number (±Infinity for upstream's infinities); TimeDelta is microseconds, DataRate bits per second and DataSize bytes. decodeEventStream() exposes the raw protobuf layer.

Development

nvm use            # Node from .nvmrc
yarn install
yarn test          # jest
yarn typecheck
yarn build         # dist/index.mjs + types/index.d.ts
yarn gen:proto     # regenerate src/gen from proto/ (needs protoc)
sh tools/cpp-vectors/build.sh   # refresh encoder test vectors from the C++ in cpp/ (needs c++ and abseil)
sh tools/cpp-golden/build.sh    # rebuild the golden logs with the upstream encoder + parser (needs clang++, cmake, ninja, abseil, protobuf, gtest)

test/logging/rtc-event-log/golden/ holds logs written by the upstream C++ encoder together with a JSON dump of what the upstream C++ parser reads from them; the test suite checks that the port reads exactly the same.

cpp/ (gitignored) is a blob-less sparse clone of libwebrtc at the pinned revision, used as the porting reference:

git clone --filter=blob:none --no-checkout https://webrtc.googlesource.com/src cpp
git -C cpp fetch origin refs/branch-heads/8037:refs/remotes/origin/branch-heads/8037
git -C cpp sparse-checkout set --no-cone /logging/rtc_event_log/ /modules/rtp_rtcp/ /api/ /rtc_base/ /system_wrappers/ /call/version.cc /experiments/
git -C cpp checkout origin/branch-heads/8037

Releasing

Releases are published to npm by .github/workflows/publish.yml with npm trusted publishing (OIDC, with provenance); no npm token is stored in the repository. Bump version in package.json, commit, then publish a GitHub release tagged v<version> — the workflow checks the tag, runs the type check, tests and build, and runs npm publish.

Related

goog-cc-as — libwebrtc's GoogCC congestion controller in AssemblyScript; it will use this parser to replay real event logs through its controller.

License

BSD 3-Clause, same as libwebrtc — see LICENSE. The original code is © The WebRTC project authors; libwebrtc's additional patent grant applies to the upstream implementation.