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/client

v0.1.0

Published

Experimental headless browser runtime for Adaptif. React apps should use @adaptif/react.

Downloads

371

Readme

@adaptif/client

Experimental headless browser runtime for Adaptif. @adaptif/react is the supported way to render decisions. Use this package when the application is not React, or when Adaptif should drive side effects instead of JSX.

The API can change in any 0.x release.

npm install @adaptif/core @adaptif/client
import { defineAdaptif } from "@adaptif/core";
import { createAdaptifClient } from "@adaptif/client";

const config = defineAdaptif<{ currentPage: string }>()({
  situations: {
    "The user is unaware of the copilot": { id: "unawareOfCopilot" },
  },
  goals: ["copilot_draft_started"],
  events: ["brief_section_revised"],
});

const adaptif = createAdaptifClient(config, {
  endpoint: "/api/adaptif",
});

adaptif.setState({ currentPage: location.pathname });

const unsubscribe = adaptif.when("unawareOfCopilot", (decision, exposure) => {
  if (!decision.active) return;
  // Calling the listener does not count as a display.
  // Record an exposure when the app handles the decision, including the
  // holdout arm, where it keeps the normal UI.
  exposure.recordExposure();
});

adaptif.emit("brief_section_revised", "tradeoffs");
adaptif.track("copilot_draft_started");
unsubscribe();
adaptif.destroy();

when, match, and gauge are typed from adaptif.config.ts. An unknown question throws. Timeouts, errors, and a false onlyIf leave the decision inactive (active: false, value: null, or level: null). The client starts automatically. With autostart: false, subscriptions stay inactive until start() is called. destroy() is terminal and prevents later subscriptions or outcome recording.

React is the better fit when a decision should choose JSX, when cleanup and re-rendering should be automatic, or when holdouts should record exposures from what actually rendered. <When> and useSituation stay the supported rendering API and are implemented on this runtime.

React apps install @adaptif/react, which depends on this package. A server route still comes from @adaptif/server.

@adaptif/client/internal is the adapter surface @adaptif/react builds on. It isn't a supported import for applications and can change in any release.