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

@sipphq/sipp-server-darwin-x64

v0.1.1

Published

Native macOS x64 binaries for Sipp Node.js server bindings

Readme

Sipp Server for Node.js

lib/node is the Node.js package source for the public @sipphq/sipp-server package. It exposes Sipp's native client API to Node server processes for local GGUF inference, gateway-backed inference, provider descriptors, and token streaming.

Source builds use the workspace manifest in this directory. Public docs use the @sipphq/sipp-server package target. Applications own framework routes and call client.query(), client.chat(), or client.embed() inside those routes.

Source Checkout

From the repository root, after source ./setup.sh:

sipp build node --backend cpu && node examples/node/query.mjs <model.gguf> "Explain Sipp."

sipp forwards to cargo xtask; use cargo xtask ... with the same arguments if the launcher is not active.

Set SIPP_NODE_BACKEND=cpu|vulkan|cuda|metal to choose a native backend.

Local GGUF Query

import { SippClient } from '@sipphq/sipp-server';

const client = new SippClient();
await client.add('default', {
  kind: 'local',
  modelPath: process.argv[2],
  config: {
    context: { n_ctx: 2048 },
    scheduler: { continuous_batching: true, prefill_chunk_size: 0 },
    cache: { mode: 'live_slot_prefix' },
    observability: { runtime_metrics: true },
  },
});

const run = client.query({
  prompt: 'Explain Sipp in one sentence.',
  emitTokens: true,
  options: { maxTokens: 64, temperature: 0.7 },
  local: { contextKey: 'node-local' },
});

let streamed = '';
for await (const batch of run) {
  streamed += batch.text;
}
const response = await run.response;
console.log(streamed || response.text);
await client.close();

Gateway clients use kind: 'gateway' descriptors when a Node process calls a separate Sipp gateway.

Gateway Profile Helpers

Use the gateway profile helpers when a Node route should behave like a first-party gateway endpoint for browser kind: 'gateway' clients:

import {
  SippClient,
  decodeGatewayQueryBody,
  gatewayErrorResponse,
  gatewayTextResponseBody,
  gatewayTextStreamResponse,
} from '@sipphq/sipp-server';

export async function handleQuery(request: Request): Promise<Response> {
  try {
    const decoded = decodeGatewayQueryBody(await request.json());
    const client = new SippClient();
    const endpoint = await client.add('gateway', {
      kind: 'gateway',
      target: decoded.target,
      baseUrl: process.env.SIPP_GATEWAY_URL!,
      authentication: {
        kind: 'bearer',
        value: process.env.SIPP_GATEWAY_TOKEN!,
      },
    });
    const run = client.query({ ...decoded.request, endpoint });
    return decoded.stream
      ? gatewayTextStreamResponse(run)
      : Response.json(
          gatewayTextResponseBody(decoded.target, await run.response),
        );
  } catch (error) {
    const response = gatewayErrorResponse(error);
    return Response.json(response.body, response.init);
  }
}

decodeGatewayChatBody(), decodeGatewayEmbedBody(), gatewayTextResponseBody(), and gatewayEmbeddingResponseBody() mirror the first-party gateway JSON profile used by Sipp clients.

Learn More