Fixing JavaScript observability, one library at a time

Summary

JavaScript application performance monitoring tools rely on monkey-patching via require-in-the-middle and import-in-the-middle, which breaks with ECMAScript Modules, bundlers, and non-Node runtimes. To solve this, an initiative is replacing monkey-patching with Node's built-in diagnostics_channel TracingChannel API across server-side JavaScript libraries. Under this pattern, libraries publish structured events while monitoring vendors subscribe to them with zero overhead when unlistened. The author leveraged Claude Code workflows alongside direct maintainer communication to draft proposals, implement code, and manage reviews across 44 target packages. Ten libraries including mysql2, node-redis, ioredis, and unjs modules have merged support, while active efforts continue on shared OpenTelemetry mapper registries and remaining ecosystem packages.

Takeaways

1. 1

   TracingChannel operates with zero overhead when no subscribers are listening, works across Node, Bun, and Deno, and avoids loader hooks or bundler conflicts.

2. 2

   Adoption is progressing across 44 tracked libraries, with 10 already merged, including mysql2, node-redis, ioredis, h3, srvx, and unstorage.

3. 3

   A planned shared mapper registry will translate TracingChannel events into standardized OpenTelemetry semantic conventions so multiple APM vendors avoid duplicated consumer mapping.