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

@marz32one/otel-rxjs-ws

v0.2.6

Published

RxJS webSocket-aligned OpenTelemetry trace propagation (embedded + header envelope; compatible with instrumentation-go/otel-gorilla-ws)

Readme

@marz32one/otel-rxjs-ws

RxJS webSocket-style OpenTelemetry instrumentation, aligned with instrumentation-go/otel-gorilla-ws.

This package is ESM-only ("type": "module"). Run npm run build so dist/ exists before consuming from file: or npm.

Subprotocol negotiation and wire format

By default (no protocol in config), the client offers ['otel-ws'] and automatically falls back to a plain connection if the server rejects it.

| Config | Offer sent | Result | |--------|-----------|--------| | No protocol (default) | ['otel-ws'] | Envelope mode if server accepts; passthrough if rejected (auto-retry) | | Explicit empty ('' / []) | [] | Passthrough mode — no otel-ws offer | | protocol: 'json' | ['otel-ws+json', 'json'] | Envelope mode if server accepts otel-ws+json | | prependOtelSubprotocol: false | user protocols only | otel-ws token never offered |

Envelope mode is active when the server returns otel-ws or otel-ws+<subprotocol> in the handshake. Each message is wrapped:

{ "header": { "traceparent": "00-…", "tracestate": "…" }, "data": { "your": "payload" } }

Passthrough mode (no envelope, no payload changes): spans are still created, but no trace context is injected into messages.

Automatic fallback: when the default offer is used and the server closes the connection before open (strict subprotocol validation), the client retries once without any subprotocol and connects in passthrough mode. No configuration needed.

Protocol activation is detected via the WebSocket open event. On close, pending context queues are cleared to prevent stale contexts from bleeding across reconnects.

Install

npm install @marz32one/otel-rxjs-ws @opentelemetry/api rxjs

Usage

import { webSocket } from '@marz32one/otel-rxjs-ws/webSocket';
// same as: import { webSocket } from '@marz32one/otel-rxjs-ws';

// Default: offers ['otel-ws'], falls back automatically if server rejects it.
const ws = webSocket<MyType>({ url: 'ws://localhost:8082/ws' });
ws.subscribe({ next: console.log, error: console.error });
ws.next({ foo: 'bar' });
ws.complete();

// Legacy server that only negotiates 'json' — skip otel-ws offer entirely.
const wsLegacy = webSocket<MyType>({
  url: 'ws://legacy-server/ws',
  protocol: 'json',
  prependOtelSubprotocol: false,
});

Spans created

| Path | Span name | Kind | |------|-----------|------| | next (outgoing) | websocket.send | Producer | | Incoming message | websocket.receive | Consumer |

websocket.receive is a child of the extracted sender context when trace context is present.

Diagnostic logging

The package logs via @opentelemetry/api's diag — silent by default. Enable in your app entry point:

import { diag, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api';
diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG);

| Level | Events logged | |-------|--------------| | DEBUG | JSON parse fallback on receive | | WARN | Custom serializer returned non-string (trace wrapping skipped) | | ERROR | Serialization failure; custom deserializer threw |

License

Apache-2.0