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

@honeystick/react

v0.80.1

Published

Honeystick provider and hooks for React

Downloads

391

Readme

@honeystick/react

React provider and hooks for Honeystick billing.

npm i @honeystick/react honeystick
import { HoneystickProvider, useCustomer } from '@honeystick/react';

<HoneystickProvider pathPrefix="/billing" includeCredentials>
  <App />
</HoneystickProvider>;

function Account({ planId }: { planId: number }) {
  const { data: plan, check, track, cancel, updateCard } = useCustomer({ planId });

  const gate = check({ featureId: 'deliveries' });
  if (!gate.allowed) return <Upgrade />;

  return <button onClick={() => track({ featureId: 'deliveries' })}>Use one</button>;
}

The provider carries no key — it builds the SDK's proxy client, which calls the handler mounted on your own server.

Hooks

| Hook | What it answers | | --- | --- | | useCustomer({ planId }) | one plan, its usage counters, and check / track / activate / cancel / updateCard | | useListPlans() | the plans on offer — what a pricing table renders from | | useListFeatures() | the features plans can meter |

Name the plan. Without planId the hook takes the newest subscription on the whole organization, which on any shared organization hands whoever opens the page somebody else's subscription.

check is answered from the plan already loaded, so a feature gate costs no request and is free to call while rendering. track goes to the server, and a capped feature answers 403 with the counter untouched — catch it and read HoneystickError.isLimitReached, which is a branch to handle rather than a fault.

Also exports HoneystickFab, the way back to Honeystick from anywhere in an integration.

The rule this SDK is built around

A secret key never reaches a browser or an app bundle. That is why there are two clients: createHoneystick() holds the key and runs on a server, and createHoneystickClient() holds nothing and calls a handler mounted on your server, which attaches the key on the way through.

ESM only, with type declarations. Requires Node 18+.

Full documentation, and five sample stores using it, at github.com/honeystick/honeystick-dev.

MIT © Honeystick