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

@structure-ai/ai

v0.0.9

Published

LLM provider bindings on @effect/ai: typed calls, structured output, resilience, token/cost observability, scripted test model.

Readme

@structure-ai/ai

Provider-agnostic LLM bindings on @effect/ai for agentic apps: typed calls with structured output, per-call deadlines, bounded retries on transient failures only, token metrics — and a deterministic scripted model so nothing in your tests touches the network. API keys stay Redacted; prompt bodies never land in logs or spans.

Usage

import { aiSettings, generateObject, generateText, layerFromSettings, TestModel } from "@structure-ai/ai";
import { load } from "@structure-ai/config";
import { Effect, Schema } from "effect";

const program = Effect.gen(function* () {
  const settings = yield* load(aiSettings);          // AI_PROVIDER, AI_MODEL, AI_API_KEY, ...
  const text = yield* generateText({ prompt: "Summarize the incident." });
  const triage = yield* generateObject({
    prompt: "Classify this ticket.",
    schema: Schema.Struct({ severity: Schema.Literal("low", "high"), reason: Schema.String }),
  });
});
// production: Effect.provide(program, layerFromSettings(settings))
// tests:      Effect.provide(program, TestModel.scripted(["a summary", { severity: "low", reason: "..." }]).layer)

Exports

| Export | What it is | | --- | --- | | aiSettings | @structure-ai/config settings: provider (anthropic|openai), model, AI_API_KEY secret, base URL, timeout (60s), max retries (2). | | layerAnthropic / layerOpenAi / layerFromSettings | LanguageModel layers (HTTP via fetch; no SDKs). | | generateText(opts) | Effect<{ text, usage: { inputTokens, outputTokens } }, AiCallError, LanguageModel>. | | generateObject({ schema, ... }) | Structured output decoded against your Schema; malformed output is a typed failure, not a defect. | | streamText(opts) | Streaming passthrough (classified errors + span; no retry — replaying a partly-consumed stream is unsafe). | | AiCallError / classifyAiError | Provider-agnostic error with classification; transport + HTTP 408/429/5xx → transient, other 4xx and malformed IO → permanent. Only transient failures are retried (exponential backoff + jitter). | | TestModel.scripted(responses, opts?) | Deterministic model layer returning scripted responses (strings, objects, or AiErrors) with fake usage; exposes calls() for attempt-count assertions. |

Every call runs in an ai.generate span (provider/model attributes only) with ai_generate boundary metrics and ai_tokens_input_total / ai_tokens_output_total counters.