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

@telorun/debug-wire

v0.4.6

Published

The Telo debug wire format: language-neutral frame contract (kernel events + log lines) shared by the producer, runner, editor, and debug UI.

Readme

@telorun/debug-wire

The Telo debug wire format — the language-neutral frame contract that flows between a kernel runtime (the producer) and every consumer of its debug stream.

A single stream carries two discriminated frame kinds:

  • kind: "event" — a kernel event (Server.Listening, MyKind.MyName.Invoked, …).
  • kind: "log" — one line of the runtime's stdout/stderr.

Consumers route on kind; a frame with no kind is treated as an event, so a legacy event-only stream still parses.

This package is intentionally tiny and browser-safe (no Node built-ins, no framework). It is the shared seam so the CLI producer, the runner that relays the stream, the editor, and @telorun/debug-ui all agree on the shape without a wrong-direction dependency on a UI package.

wire-schema.json is the source of truth a non-TypeScript producer (a future Rust/Go kernel) conforms to; the TypeScript types here are its projection.

Kernel events a host may depend on

The dotted event vocabulary inside an event frame is open — a kind emits <Name>.Invoked, <Name>.Listening and whatever else it has to say, and no consumer is obliged to know any of them. These four are the exception: a HOST (the runner that stands a workload up and routes traffic to it) derives observable behaviour from them, so a kernel that does not emit them leaves that host with no run outcomes and no way to re-route a port. They are listed here rather than left to one implementation because a second runtime has to be able to implement against them.

| Event | Payload | What a host does with it | | --- | --- | --- | | Kernel.Starting | { telo?: string } | Opens a run generation. telo is the version the runtime reports for itself (X, or X+unreleased for a build made while X is pending); a runtime released before the field existed sends none. | | Kernel.Stopped | { exitCode: number } | Closes it, carrying the code. | | Kernel.RunFailed | { phase: "load" \| "start", code?: string, message: string, unresolved?: Array<{ id: string, block: "variables" \| "secrets" \| "ports" \| "needs", name: string, env?: string, arg?: string, sensitive: boolean, type: string, schema: object, title?: string, description?: string, refusal?: string }> } | Reports a generation that never reached a running state, with the diagnostic code where there is one. Emitted where Kernel.Starting never fires (a manifest that fails to LOAD) or fires and is never followed by Kernel.Stopped (a boot failure). unresolved, present when the load was refused only because inputs have no value, names each of them by its declaration (variables.clientId, needs Orders.databaseAccess.url) with what a host needs to ask for it — never a value; a runtime released before the field existed sends none. | | Kernel.PortsResolved | { ports: Array<{ name: string, port: number, protocol: "tcp" \| "udp", publicUrls?: Array<{ need: string, host: string }> }> } | Re-routes the workload. The Application's ports: block resolved to integers, re-emitted on every load — so a host patches its routing without re-parsing a manifest. DECLARED, not bound: whether anything is listening is a separate observation. publicUrls, present when a Telo.PublicUrl need names the port, lists each such need with the host its URL resolved to — the hosts a host deriving addresses from TELO_HOST_PUBLIC_URL_TEMPLATE routes to the port; a runtime released before the field existed sends none. |

A host reads these tolerantly. A payload it cannot make sense of is skipped, not failed on: it consumes a stream from a kernel it is not versioned with.

A stream that carries a replay buffer MUST put a monotonic id: on each frame and honour Last-Event-ID. Without a resume point a reconnecting consumer is replayed history it has already seen — and a consumer that DERIVES state from the stream (a host counting run generations) then counts it twice.

Surface

  • Types: DebugFrame (= DebugEvent | DebugLog), DebugEvent, DebugLog, WireRef, WireBlob.
  • Guards: isLogFrame, isEventFrame, isWireRef, isWireBlob.
  • Helper: eventSuffix(event) — the trailing segment of a dotted event name.