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

@offstage/react

v0.0.2

Published

React bindings for the Offstage analytics SDK

Readme

@offstage/react

React bindings for the Offstage browser SDK. Works with React 19, Server Components, and TanStack Start / Next.js / Remix out of the box.

Install

pnpm add @offstage/react react

@offstage/browser is bundled as a regular dependency — you don't need to install it explicitly.

Quick start

Wrap your app once at the root:

import { OffstageProvider } from "@offstage/react";

export function App({ children }: { children: React.ReactNode }) {
  return <OffstageProvider apiKey="pk_live_...">{children}</OffstageProvider>;
}

Then track from any client component:

"use client";

import { useOffstage } from "@offstage/react";

export function SignupButton() {
  const { track, identify } = useOffstage();

  return (
    <button
      onClick={() => {
        identify("user_123", { plan: "pro" });
        track("signup_completed");
      }}
    >
      Sign up
    </button>
  );
}

API

<OffstageProvider />

| Prop | Type | Default | Description | | --------------- | ----------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | apiKey | string | — | Your Offstage publishable API key. | | host | string | — | Override the ingest host (self-hosted deployments). | | autoPageviews | boolean | true | Emit a pageview on initial mount and on history navigation. | | consent | boolean | true | Pass false to no-op until you re-render the provider with true. | | enabled | boolean | auto | Hard kill switch. When omitted, auto-disables on localhost / 127.0.0.1 so dev traffic doesn't pollute production. Pass true to force-on or false to force-off. | | children | ReactNode | — | Your tree. |

The provider is SSR-safe: it doesn't instantiate the SDK during server rendering.

useOffstage()

Returns { track, identify, pageview } bound to the active provider. Throws if called outside <OffstageProvider> — that's a wiring bug, not a tracking error, so it surfaces loudly.

const { track, identify, pageview } = useOffstage();

track("event_name", { foo: "bar" });
identify("user_id", { email: "..." });
pageview("/custom-path"); // optional, defaults to current path

See @offstage/browser for the underlying tracking semantics, payload shape, and storage model.