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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mixpa

v0.4.0

Published

Mixpanel client for app events

Downloads

24

Readme

mixpa

npm Bundle size Code style: Prettier Donate

Tiny, isomorphic client for Mixpanel

Usage

import { create } from 'mixpa'

export const mp = create({
  token: '2418e6a0238911541536b590a76e2b01',
  debug: false,
})

Options

  • token: string
    Your project token.

  • baseUrl?: string
    The domain to send requests to.

  • debug?: 0 | 1 | 2 | 3
    Debug your requests. Higher values inherit the effects of lower values.

    • 1: Log requests to the console.
    • 2: Enable verbose error messages.
    • 3: Skip sending requests entirely.
  • onError?: (error: Error, req: MixpaRequest) => void
    Control what happens when a request fails. You can rethrow the error to force the original caller to handle it, but rethrown errors for non-critical requests are just logged to the console.

  • queueSend?: (send: () => void, method: string, data: object) => void
    Control when each request is sent. For example, you might wait for a network connection.
    By default, requests are sent immediately.

 

Event Types

Tracked events can be strongly typed.

type Events = {
  openApp: void
  sharePost: { postId: string }
}

export const mp = create<Events>({ ... })

mp.track('sharePost') // Error: "sharePost" is not assignable to "openApp"

 

Automatic Retries

Using the onError option, you can implement logic for automatically retrying a failed request.

Here's an example that uses backo2 for exponential backoff:

import { MixpaRequest, noRetryStatus } from 'mixpa'
import Backoff from 'backo2'

function onError(error: Error, req: MixpaRequest) {
  // If this error is from a retried request, rethrow it so the retry
  // handler is notified. Otherwise, rethrow it only when it's obviously
  // not a network disconnection.
  if (req.isRetry || (req.status == noRetryStatus && navigator.onLine)) {
    throw error
  }
  return new Promise<void>((resolve, reject) => {
    const backoff = new Backoff()

    function scheduleRetry() {
      if (backoff.attempts == 10) {
        // For critical requests, this will reject their promise.
        // Otherwise, the error is just logged to console.
        return reject(error)
      }
      setTimeout(() => {
        req.retry().then(resolve, scheduleRetry)
      }, backoff.duration())
    }

    scheduleRetry()
  })
}

 

Notes

  • No properties are ever set automatically.
  • You'll want to call setState with "reserved" properties (eg: $device_id) before you track any events.
  • You must've called setUser with a string before you can call setUserProps.

 

API

To track an event:

mp.track('My Event', { ... })

 

To identify the user:

mp.setUser('6ab86a11-9958-4afd-bf01-7a06d8d3f8a4')

 

To forget the user:

mp.setUser(null)

 

To update user-specific properties:

mp.setUserProps({ ... })

 

To send properties with every track call:

mp.setState({ ... })