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

@adaptif/server

v0.1.0

Published

The Adaptif server: request handler, providers, and outcome sinks.

Readme

@adaptif/server

The request handler, provider adapters, and outcome sinks that run on the developer's own server. The main entry is Fetch-API–based and has no Node-only dependencies, so it runs unmodified on Cloudflare Workers, Next.js Route Handlers, or any other Fetch-compatible runtime. Node-only concerns (the JSONL sink) live under the @adaptif/server/node subpath.

npm install @adaptif/core @adaptif/server

providerFromEnv() builds typesafe(), openrouter(), or vercelGateway() from the server environment (TYPESAFE_API_KEY, then OPENROUTER_API_KEY, then AI_GATEWAY_API_KEY). @adaptif/next wraps createHandler as a Next.js route; other Fetch runtimes can mount the handler directly. The config object you pass is the allowlist in every environment.

Both routes require Content-Type: application/json and send no CORS headers, so they answer same-origin requests only. With debug off, a failing or timed-out provider logs one warning per minute with the error class only. See Production hardening for rate limits and timeouts.

The model-vs-rule eval behind the README's results lives in the repository at packages/server/scripts/eval/; it isn't part of the published package.

Outcome sinks

POST …/outcome validates outcome events, adds receivedAt, session, assignmentKey, and schema: 1 (never IP addresses or user agents), and passes them to createHandler's sinks. A failing sink is logged by name and never fails the request. Outcome requests are rate-limited like evaluate requests (by default 30 per session per minute).

  • consoleSink(): one line per event, for development.
  • jsonlSink(path) (@adaptif/server/node): appends JSON lines, creating directories, with writes serialized. Needs a persistent disk: on serverless hosts (Vercel, Netlify, Cloudflare, Lambda) use webhookSink or your own sink.
  • webhookSink(url, { headers?, batchMs?, timeoutMs? }): POSTs JSON arrays with a timeout and one retry.
  • multiSink(...sinks): writes to several sinks; one failing doesn't stop the others.
  • Your own: { name, write(events: readonly StoredOutcomeEvent[]) }. The event format is @adaptif/core/outcome-schema.json.