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

@logclip/react

v0.5.3

Published

React adapter for the LogClip tracker — <LogClipProvider> and useLogClip().

Readme

@logclip/react

The React adapter for the LogClip capture SDK. One provider at the root of your app starts recording, and a hook gives any component the client.

It exists for one reason that is easy to get wrong by hand: identity usually arrives late. A session starts the moment the page loads, but you do not know who the user is until the auth call comes back. Pass userId as a prop and the provider calls identify() for you the moment it resolves, which retro-stamps the session that is already in flight — the recording from before login belongs to the right person.

Install

npm install @logclip/react @logclip/tracker

Use

import { LogClipProvider } from '@logclip/react';

export function App({ user }) {
  return (
    <LogClipProvider
      siteKey="pk_live_xxx"
      endpoint="https://in.yourapp.com"
      userId={user?.id}                      // may be undefined on first render
      metadata={{ plan: user?.plan }}
    >
      <Routes />
    </LogClipProvider>
  );
}

Anywhere below it:

import { useLogClip } from '@logclip/react';

function Checkout() {
  const logclip = useLogClip();

  return (
    <button onClick={() => {
      logclip.track('checkout_started', { cart: 3 });
      logclip.conversion('checkout');
    }}>
      Pay
    </button>
  );
}

Props

LogClipProvider takes every option LogClip.init() takes — siteKey, endpoint, maskAllInputs, requireConsent, sampleRate and the rest, all documented in @logclip/tracker — plus two that it manages for you:

| Prop | Notes | |---|---| | userId | Your own user id. Applied via identify() on mount and again whenever it changes, so late login and account switching both work. | | metadata | Searchable session properties. Re-merged via setMetadata() whenever the object changes. |

What the hook returns

The LogClip client itself, so everything the SDK can do is available:

identify(userId, traits?)   setMetadata(props)   reset()
track(name, props?)         conversion(name, props?)   tag(...names)
startTask(name) / endTask(name)
setConsent(granted)         startRecording() / stopRecording()
flush()                     stop()
sessionId

Call reset() on logout. It forgets the identity and starts a fresh anonymous session rather than attributing the next visitor to the last one.

Notes

  • Safe to mount twice. init() is idempotent, so React 18 StrictMode's double-mount does not start two recorders, and a provider added to a page that already boots the tracker from a script tag defers to the one already running.
  • Consent. With requireConsent, nothing leaves the page until you call setConsent(true) from the hook.
  • Older names. ObsrviqProvider and useObsrviq are exported as aliases and are not going away, so existing apps keep compiling. New code should use the LogClip names.
  • React Native is a separate package: @logclip/react-native.

MIT licensed.