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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@metro-fs/analytics-plugin-posthog

v1.14.0

Published

PostHog plugin for Analytics

Downloads

4,125

Readme

@metro-fs/analytics-plugin-posthog

Important note for the initial release

If your project is using Typescript, you'll get an error when trying to use custom methods defined in this plugin: Property 'posthog' does not exist on type 'Plugins'. Custom methods are working fine, base library needs a change in typing for the plugins array.
You can track the issue HERE.

What's that

This is a small plugin for DavidWells/analytics library. It handles all basic analytics library methods (initialize, page, track, identify, and loaded). Initially, we were adding selected custom methods that PostHog's API provides one by one (like register, trackAndSet, trackAndSetOnce, etc.), but it required releasing a new version with each change. Currently, we have exposed a scoped instance of PostHog itself; you can get it with analytics.plugins.posthog.getPosthogInstance.

Installation

  1. npm i @metro-fs/analytics-plugin-posthog
  2. In analytics init, add PostHog in the plugins array. Example config:
import Analytics from 'analytics';
import postHog from '@metro-fs/analytics-plugin-posthog';

const analytics = Analytics({
  app: 'example',
  plugins: [
    postHog({
      token: POSTHOG_TOKEN,
      enabled: true,
      options: {
        api_host: POSTHOG_API_HOST,
        debug: process.env.NODE_ENV === 'dev',
        persistence: 'memory',
        disable_cookie: true,
        disable_session_recording: true,
      },
    }),
  ],
});

export default analytics;

Usage

Just use the analytics library as usually, e.g. analytics.track(eventName, eventValue);.
If you want to use custom PostHog methods, use: analytics.plugins.posthog.onFeatureFlags(this.onFeatureFlagsReady). Please remember about the TypeScript issue mentioned earlier.

Identify

You can use default behavior of all Analytics plugins and then all user traits will end up as $set property and $set_once will be empty.

Or you can manually specify $set and $set_once, that will override all other traits:

analytics.identify(userId, {
  propertyName1: 'value1',
  propertyName2: 'value2',
  $set: {
    propertyName3: 'value2-overriden',
    propertyName4: 'value3',
  },
  $set_once: {
    propertyName5: 'value4',
  }
})

that will ignore propertyName1 and propertyName2 and send $set and $set_once directly