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

jomolhari

v1.0.17

Published

Interactive CLI for enriching and aggregating FullStory data.

Downloads

2

Readme

jomolhari

A user analytics CLI that pulls user data from FullStory data export feature.

Usage

You can use the CLI interactively or by passing command line arguments.

To get started, let's install the package: npm i jomolhari -g.

Next, we need to create a story.js file in the root of our project. The story.js allows us to configure the CLI with the various options:

  • apiKey: This is the API key you get out of FullStory. This is required.
  • routes: This is a array of { route: string, page: string } that we can normalize our routes to. The routes table uses path-to-regexp under the hood to allow you to normalize complex URLs to human readable ones.
  • transforms: This is a key/value map of properties we can use to transform data attributes.
  • blacklists: This is a key/value map of properties that we want to exclude certain values from.

An example story.js might look like:

module.exports = {
  "apiKey": "XXXXXXXXXXXXXXXXXXXXX",
  "blacklists": {
    "Customer": [
      "sandbox",
    ],
    "UserEmailDomain": [
      'user.com'
    ]
  },
  "transforms": {
    "Customer": (data) => {
      return data.PageUrlOrigin.replace('https://', '')
    }
  },
  "routes": [
    { "route": "/dashboard", "page": "/dashboard" },
    { "route": "/users/:id", "page": "/users/details" },
    { "route": "/users/:id/:tab?", "page": "/users/details" }
  ]
};

Now that everything is configured, we can run our CLI. The CLI can be ran interactively which allows a user to type in values dynamically or via command line arguments.

To run the CLI interactively, you can do sbc or if you want to run it your command line arguments like: sbc --offset=1 --type=JSON --aggregate=true.