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

@string-os/client

v0.1.0

Published

HTTP/SSE client for stringd — talk to a running String daemon from any Node.js or TypeScript program

Readme

@string-os/client

HTTP/SSE client for stringd — talk to a running String daemon from any Node.js or TypeScript program. No runtime dependencies (uses only Node's built-in http module).

This is the same client library that @string-os/string's CLI uses internally. Extracted as a standalone package so you can write a custom tool that speaks to stringd without pulling in the full runtime.

Install

npm install @string-os/client

Prerequisites

You need a running stringd daemon. The simplest path:

npm install -g @string-os/string
string --daemon start

Default port is 3100. Change with STRINGD_PORT=... in the daemon's environment.

Usage

import { ping, ensureUser, exec } from '@string-os/client';

const port = 3100;
const userId = 'default';
const home = '/home/alice/.string/users/default';

// 1. Check the daemon is alive
const alive = await ping(port);
if (!alive) throw new Error('stringd not running on port ' + port);

// 2. Make sure the user exists (idempotent)
await ensureUser(port, { id: userId, home });

// 3. Execute a command in a topic
const result = await exec(port, userId, 'file:main', '/open ./README.md');

console.log(result.ok);       // true
console.log(result.code);     // null on success, error code on failure
console.log(result.content);  // the command output
console.log(result.meta);     // current document metadata or null

API

ping(port: number): Promise<boolean>
ensureUser(port: number, user: { id: string; home: string }): Promise<void>
exec(port: number, userId: string, topic: string, cmd: string, requestId?: string): Promise<ExecResult>
health(port: number): Promise<{ ok: boolean; users: number; sessions: number }>
shutdown(port: number): Promise<void>

// SSE utilities
parseSSE(raw: string): Array<{ event: string; data: string }>
sseToExecResult(raw: string): ExecResult
stripContentPrefix(raw: string): string

interface ExecResult {
  ok: boolean;
  code: string | null;
  content: string;
  meta: object | null;
}

Protocol

The client speaks stringd protocol v0.1. If you want to implement this protocol in another language, start there — the spec is the source of truth, not this TypeScript client.

Related

License

MIT