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

tigr-react-native

v0.1.5

Published

tigr analytics SDK for React Native & Expo — drop-in capture of app lifecycle, sessions and errors.

Downloads

648

Readme


tigr is a product analytics platform that turns raw events into clear, actionable insights. No charts to decode, no data team required — you install the SDK, and tigr does the rest. This package is the React Native / Expo client.

Install

npm install tigr-react-native @react-native-async-storage/async-storage

AsyncStorage is a peer dependency (used to persist the visitor id across launches). Already using MMKV or another store? Pass your own adapter via the storage option — see Configuration.

Quick start

Wrap your app once with your project API key. Sessions, app lifecycle (foreground/background) and uncaught errors are captured automatically.

import { TigrProvider } from 'tigr-react-native'

export default function App() {
  return (
    <TigrProvider config={{ apiKey: 'tigr_pk_...' }}>
      <RootNavigator />
    </TigrProvider>
  )
}

Get your API key from your project's Settings at usetigr.app.

Tracking custom events

Grab the client in any component with useTigr():

import { useTigr } from 'tigr-react-native'

function UpgradeButton() {
  const tigr = useTigr()
  return (
    <Button title="Upgrade" onPress={() => tigr.track('upgrade_pressed', { plan: 'pro' })} />
  )
}

Identifying users

const tigr = useTigr()

tigr.setUser(user.id, { name: user.name, email: user.email }) // on login
tigr.reset()                                                  // on logout

identify() is the same as setUser() — use whichever reads better.

Screen tracking

There's no automatic pageview on mobile — emit a screen_view on navigation:

// React Navigation
<NavigationContainer
  onStateChange={() => {
    const name = navigationRef.getCurrentRoute()?.name
    if (name) tigr.track('screen_view', { screen: name })
  }}
>

Configuration

<TigrProvider
  config={{
    apiKey: 'tigr_pk_...',
    autoCapture: true,        // true | false | { lifecycle, error }
    flushInterval: 2000,      // ms before a buffered batch is sent (default 2000)
    batchSize: 20,            // force a flush at this many events (default 20)
    debug: false,             // log every event + flush to the console
    devMode: false,           // when true, the SDK does nothing (use in development)
  }}
>

| Option | Type | Default | Description | | --------------- | ------------------------------------- | ------- | ----------- | | apiKey | string | — | Required. Your project API key. | | host | string | tigr cloud | Where events are sent. Override for a self-hosted / local ingestion service. | | autoCapture | boolean \| Partial<AutoCaptureOptions> | true | Toggle automatic signals individually or all at once. | | storage | StorageAdapter | AsyncStorage | Persistence adapter for the visitor id (pass your own, e.g. an MMKV wrapper). | | flushInterval | number | 2000 | Ms to wait after the first buffered event before sending. | | batchSize | number | 20 | Flush immediately once the queue reaches this size. | | debug | boolean | false | Console-log every event and flush. | | devMode | boolean | false | When true the SDK does nothing — no capture, no network. Turn it on in development so your own activity doesn't pollute analytics. |

Auto-captured signals

lifecycle (app foreground/background → app_background) · error (uncaught JS errors). Both on by default — turn either off:

<TigrProvider config={{ apiKey: 'tigr_pk_...', autoCapture: { error: false } }}>

Local development

By default events go to tigr's hosted ingestion endpoint. A device or emulator can't reach localhost, so for local testing point host at your machine's LAN IP:

<TigrProvider config={{ apiKey: 'tigr_pk_...', host: 'http://192.168.1.3:4001' }}>

Set host: '' (empty string) to run in console-only mode — events are logged but nothing is sent. Omit host entirely to use the default tigr cloud.

API

useTigr() returns the client:

| Method | Description | | ------ | ----------- | | track(name, properties?) | Send a custom event. | | identify(userId, traits?) | Tie events to a user. | | setUser(userId, traits?) | Alias for identify. | | reset() | Clear the current user (e.g. on logout). | | flush() | Send everything queued right now. |

License

MIT © tigr