Title here
Summary here
Schemas · 3.3.0
Issue lifecycle keys, a TypeScript generator rewrite, and repaired decoder imports.
Read schema changelog on GitHub ↗key field to ClientIssue in ClientSample — identifier of the related
issue or resolution when one is provided.IceCandidatePairStats.state, and source comments recording
which RTCStatsIceCandidatePairState symbols are no longer in the W3C spec:
new (never standardised) and cancelled (removed after
w3c/webrtc-stats#66; last
published in the 2016-12-14 Working Draft). Both symbols are retained for
backward compatibility — no field or enum value was removed, so the wire
format is unchanged.Wire-format warning.
ClientIssuefield numbers shift because protobuf numbering follows sorted field order:payloadmoves 2 → 3 andtimestamp3 → 4. A decoder built against 3.2.0 will misread these. Seedocs/GENERATOR.md.
src/, run with
npm run generate). The legacy index.js and its root-level helpers were
removed. Generated TypeScript, Avro and protobuf output is byte-identical to
the previous implementation.schemaVersion is now exported from the ClientSample module only. It was
previously emitted by every generated module, which made src/index.ts
re-export the same name twice and broke npm-samples-lib’s build (TS2308).
The package still exports schemaVersion from its entry point.undefined for enum fields that
have no description."module": "nodenext". Emit is still
CommonJS; published entry points are unchanged.avro-js 1.12.1, @bufbuild/buf 1.72.0,
@bufbuild/protobuf and @bufbuild/protoc-gen-es 2.13.0. Removed argparse,
json-schema-to-markdown, protobufjs and typedoc, none of which were used.@observertc/samples-decoder could not be imported. ClientSampleDecoder
imported fromBinary from @bufbuild/protobuf/dist/cjs/from-binary, a path
that stopped existing in protobuf-es v2; requiring the package threw
ERR_PACKAGE_PATH_NOT_EXPORTED. It now imports from the package root.Source: ObserveRTC schema changelog. Date verified from the schema version commit.