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

@vectorbea-ai/node

v0.2.7

Published

Official Node.js / TypeScript SDK for the VectorBea prompt management platform

Readme

@vectorbea-ai/node

Official Node.js / TypeScript SDK for the VectorBea prompt management platform.

Requirements

  • Node.js 18+

Installation

npm install @vectorbea-ai/node

Quick start

import { VectorBeaClient } from "@vectorbea-ai/node";

// API key is read from VECTORBEA_API_KEY env var by default
const client = new VectorBeaClient({
  apiKey:  "vbagent_your_token_here",  // replace with your key
  baseUrl: "http://localhost:8080",    // omit to use VectorBea Cloud
});

const prompt  = await client.prompts.get("greet-user");
const message = prompt.compile({ name: "Alice", product: "Acme AI" });
console.log(message);

With environment variables

export VECTORBEA_API_KEY=vbagent_your_token_here
export VECTORBEA_BASE_URL=http://localhost:8080  # optional
// Picks up VECTORBEA_API_KEY automatically
const client = new VectorBeaClient();
const prompt  = await client.prompts.get("customer-support-reply");
const message = prompt.compile({ customer_name: "Bob", issue: "billing" });

Audit telemetry

prompts.get() automatically records proxy fetch latency. Call logAudit() after your LLM responds to add token counts and LLM latency:

const prompt  = await client.prompts.get("greet-user");
const message = prompt.compile({ name: "Alice" });

// ... call your LLM ...

await client.prompts.logAudit(prompt, {
  llmLatencyMs: 432,
  tokenCount: 87,
  metadata: { model: "gpt-4o" },
});

Error handling

import {
  VectorBeaClient,
  AuthenticationError,
  NotFoundError,
  ConnectionError,
  TimeoutError,
} from "@vectorbea-ai/node";

try {
  const prompt = await client.prompts.get("my-prompt");
} catch (err) {
  if (err instanceof AuthenticationError) {
    console.error("Invalid API key");
  } else if (err instanceof NotFoundError) {
    console.error("Prompt not found");
  } else if (err instanceof TimeoutError) {
    console.error("Request timed out");
  } else if (err instanceof ConnectionError) {
    console.error("Could not reach the proxy");
  }
}

License

MIT — see LICENSE.