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

@theokit/presenter

v0.10.0

Published

TheoKit's presentation layer — the canonical AgentOutputEvent + Presenter Strategy that turns @theokit/sdk agent output into any surface (web UIMessageStream, terminal ANSI, JSON API) from ONE normalized event.

Downloads

5,826

Readme

@theokit/presenter

The presentation layer: one normalized agent-output event, N surfaces.

Agent output has to reach a web stream, a terminal, and a JSON API. Translating the runtime's messages separately for each of them gives you N×M translators that drift — the terminal grows a tool-call rendering the web never gets, and a new SDK event lands in one path only.

This package is the narrow waist that removes the multiplication. Every source translates into AgentOutputEvent; every presenter translates out of it.

SDK message ─┐                        ┌─→ UIMessageStreamPresenter → web
             ├─→ AgentOutputEvent ────┼─→ TerminalPresenter        → ANSI rows
wire chunk ──┘                        └─→ JsonPresenter            → records

The variants are derived from the runtime's own discriminants, never from one surface's wire format — so no surface leaks into the contract.

Install

pnpm add @theokit/presenter

Peers: @theokit/sdk and zod.

The canonical event

Eight variants, discriminated on type:

| Variant | Carries | |---|---| | text | assistant text output, streamed or whole | | reasoning | thinking content, distinct from user-visible text | | tool-call | a tool invocation with its committed input | | partial-tool-call | incremental tool input while the model streams the args | | tool-result | the result for a callId, with isError for failures | | status | run-level status | | error | a failed turn | | finish | the end of the turn plus its metadata |

Sources and presenters

import { fromSdkMessage, TerminalPresenter } from '@theokit/presenter'

const presenter = new TerminalPresenter()
for (const message of sdkMessages) {
  for (const event of fromSdkMessage(message)) {
    for (const row of presenter.present(event)) render(row)
  }
}

fromWireChunk is the other door — from the transport wire into the canonical event, which is what a client-side surface receives. fromInteractionUpdate covers interactive runs.

A Presenter<TOut> is surface + present(event), with optional start() / finish() framing for stateful surfaces. UIMessageStreamPresenter holds open-block state and is therefore instantiated per stream; TerminalPresenter and JsonPresenter are stateless and may be singletons. PresenterRegistry resolves one by surface key and throws a typed UnknownPresenterError when the key is unknown — never a silent fallback.

foldTurnLifecycle collapses a turn's events into a TurnLifecycle when a surface wants the outcome rather than the stream.

Subpaths

| Subpath | What lives there | |---|---| | . | The event, the Presenter contract, the registry, the sources, the three presenters | | ./wire | The wire-format types shared with transports |

Licence

Apache-2.0 — see LICENSE.