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

@optare/client

v0.1.0

Published

Headless, framework-agnostic client SDK for Optare. Takes a pk_live_ key and resolves endpoint + branding.

Readme

@optare/client

Headless, framework-agnostic client SDK for Optare. The entire integration contract is one string — a publishable key (pk_live_…).

import { createOptareClient } from "@optare/client";

const { auth, config } = await createOptareClient({
  publishableKey: "pk_live_xxx",
  // baseURL / configURL optional — defaults to the hosted Optare API
});

// `auth` is a better-auth client
await auth.signIn.email({ email, password });
const { data: session } = await auth.getSession();

// `config` is the resolved endpoint + white-label branding
config.baseURL;          // where the auth API lives
config.branding.name;    // customer's org name
config.branding.logoUrl; // customer's logo

What it does

  1. resolveOptareConfig() calls GET /api/public/config?pk=… and learns the auth API origin and the project's branding. pk_live_ is not a secret, so this is safe from a browser.
  2. createOptareClient() builds a better-auth client pointed at that origin with the Optare plugin set (organization, 2FA, email OTP, magic link, multi-session, JWT) and the publishable key attached to every request.

For SSR, call resolveOptareConfig() on the server and pass the result back as bootstrap to skip the client-side fetch.

Server-side use

For sk_live_ management calls or offline JWT verification, use @optare/node instead — this package is for the front end.