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

@patriceckhart/zot-sdk-javascript

v0.1.4

Published

TypeScript SDK for embedding zot RPC in Node.js applications.

Readme

@patriceckhart/zot-sdk-javascript

TypeScript SDK for embedding zot rpc in Node.js applications.

The SDK starts a long-lived zot rpc child process and talks newline-delimited JSON over stdin/stdout. It is intended for Node-compatible server runtimes. Do not import it in browser components or edge runtimes.

Install

npm install @patriceckhart/zot-sdk-javascript
# or
pnpm add @patriceckhart/zot-sdk-javascript
# or
yarn add @patriceckhart/zot-sdk-javascript
# or
bun add @patriceckhart/zot-sdk-javascript

During install, postinstall detects your OS and CPU. If zot is already on PATH, it uses that. Otherwise it downloads the matching release asset from GitHub, verifies checksums.txt, and stores the binary under the package vendor/ directory. Platform binaries are not committed to this package.

Bun

Bun may block dependency lifecycle scripts and print Blocked 1 postinstall. If that happens, either trust the package with Bun or run the installer manually after bun add:

node node_modules/@patriceckhart/zot-sdk-javascript/scripts/install-zot.js

If zot is already installed on your PATH, no download is needed.

Environment controls:

  • ZOT_SKIP_INSTALL=1: skip binary download.
  • ZOT_FORCE_INSTALL=1: download even when zot exists on PATH.
  • ZOT_VERSION=v0.2.31: pin a zot release tag.
  • ZOT_BINARY=/path/to/zot: use a specific binary at runtime.

Node.js usage

import { ZotClient } from "@patriceckhart/zot-sdk-javascript";

const zot = new ZotClient({
  provider: "anthropic",
  model: "claude-sonnet-4-5",
  cwd: process.cwd(),
});

for await (const event of zot.promptStream("Explain this project in 3 bullets")) {
  if (event.type === "text_delta") process.stdout.write(event.delta);
  if (event.type === "tool_call") console.log("\ntool:", event.name, event.args);
}

zot.close();

One-shot prompt:

import { createZotClient } from "@patriceckhart/zot-sdk-javascript";

const zot = await createZotClient({ provider: "openai", cwd: process.cwd() });
const result = await zot.prompt("Write a tiny README for this app");
console.log(result.text);
zot.close();

Framework usage

zot rpc is stateful, so keep one client per chat session on the server. The SDK works in any Node-compatible server framework that can spawn child processes. It does not work in browser code or edge runtimes.

Next.js route handler example

This minimal example streams text deltas as Server-Sent Events.

// app/api/chat/route.ts
import { ZotClient } from "@patriceckhart/zot-sdk-javascript";

export const runtime = "nodejs";

const clients = new Map<string, ZotClient>();

function getClient(sessionId: string) {
  let client = clients.get(sessionId);
  if (!client) {
    client = new ZotClient({
      provider: process.env.ZOT_PROVIDER ?? "anthropic",
      model: process.env.ZOT_MODEL,
      cwd: process.cwd(),
    });
    clients.set(sessionId, client);
  }
  return client;
}

export async function POST(req: Request) {
  const { message, sessionId = "default" } = await req.json();
  const client = getClient(sessionId);

  const stream = new ReadableStream({
    async start(controller) {
      const encoder = new TextEncoder();
      try {
        for await (const event of client.promptStream(message)) {
          if (event.type === "text_delta") {
            controller.enqueue(encoder.encode(`data: ${JSON.stringify({ delta: event.delta })}\n\n`));
          }
          if (event.type === "done") {
            controller.enqueue(encoder.encode("data: [DONE]\n\n"));
          }
        }
      } catch (error) {
        controller.enqueue(encoder.encode(`event: error\ndata: ${JSON.stringify(String(error))}\n\n`));
      } finally {
        controller.close();
      }
    },
  });

  return new Response(stream, {
    headers: {
      "content-type": "text/event-stream",
      "cache-control": "no-cache",
    },
  });
}

Nuxt server route example

// server/api/chat.post.ts
import { ZotClient } from "@patriceckhart/zot-sdk-javascript";

const zot = new ZotClient({
  provider: process.env.ZOT_PROVIDER ?? "anthropic",
  model: process.env.ZOT_MODEL,
  cwd: process.cwd(),
});

export default defineEventHandler(async (event) => {
  const body = await readBody<{ message: string }>(event);
  const result = await zot.prompt(body.message);
  return { text: result.text };
});

API

const client = new ZotClient(options);
await client.start();
await client.hello();
await client.ping();
await client.prompt("message");
client.promptStream("message");
await client.abort();
await client.compact();
await client.getState();
await client.getMessages();
await client.clear();
await client.setModel("model-id");
await client.getModels();
client.close();

Important options:

  • binary: path to zot. Defaults to ZOT_BINARY or zot.
  • provider, model, cwd, apiKey, baseUrl map to zot rpc flags.
  • auth: credential source preference, auto (default), apiKey, or subscription.
  • systemPrompt, appendSystemPrompt, reasoning, maxSteps, noTools, tools map to zot rpc flags.
  • rpcToken: sends the initial hello token when ZOTCORE_RPC_TOKEN is set on the child process.

Auth

By default, the SDK uses normal zot auth. Run zot and /login, or pass provider API keys via environment variables such as ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, KIMI_API_KEY, and others supported by zot.

To require API-key auth from SDK configuration, pass auth: "apiKey" with apiKey.

To require stored subscription credentials, first run zot and /login, choose subscription, then create the client with auth: "subscription" and a subscription-capable provider:

const zot = new ZotClient({
  provider: "openai-codex",
  auth: "subscription",
  cwd: process.cwd(),
});

Subscription auth is available for the same providers supported by zot itself: anthropic, openai-codex, kimi, and github-copilot. DeepSeek and Google do not have subscription login paths.

Notes

  • One ZotClient wraps one zot rpc process, cwd, model, and session.
  • Use it only in Node-compatible server runtimes with child process support.
  • Only one prompt or compact operation should be active per client.
  • For multiple projects or concurrent chats, create multiple clients.
  • The process exits when closed or when stdin closes.

License

MIT