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

@posthog/event-sequence-timer-plugin

v0.0.7

Published

Time the time taken for a user to perform Event B after performing Event A.

Downloads

8

Readme

Event Sequence Timer Plugin

Time the time taken for a user to perform Event B after performing Event A.

A property time_since_eventA will be added to eventB, with time measured in milliseconds.

Example Usage

Config

List of events to track time differences on

The list of events is specified as follows:

(eventA,eventB),(eventC,eventD),(eventA,eventD)

Where the first event in a tuple is the event that "starts the timer" and the second event being the one that "finishes it". In other words, the first event happens before the second.

Update timestamp on every new first event?

Default: Yes

If you select Yes, the stored timestamp for the first event will always be updated when a new event with the same name comes in (for the same user). This means your second event will always contain the difference between its time and the last time the user triggered the first event.

If you select No, the stored timestamp will only be set once and never updated. This means you will get the difference between the time of the second event and the first time the user triggered the first event.

Example 1:

Config

List of events to track time differences on: (eventA,eventB) Update timestamp on every new first event? Yes

User events

eventA at t=0
eventA at t=2
eventB at t=4

Result

eventB will come with a property time_since_eventA equal to 2.

Example 2:

Config

List of events to track time differences on: (eventA,eventB) Update timestamp on every new first event? No

User events

eventA at t=0
eventA at t=2
eventB at t=4

Result

eventB will come with a property time_since_eventA equal to 4.