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

insight

v0.11.1

Published

Understand how your tool is being used by anonymously reporting usage metrics to Google Analytics or Yandex.Metrica

Downloads

1,060,245

Readme

Insight Build Status

Understand how your tool is being used by anonymously reporting usage metrics to Google Analytics or Yandex.Metrica

Install

$ npm install insight

Access data / generate dashboards

Google Analytics (GA)

analytics screenshot

Provider Setup

Google Analytics (GA)

Currently, Insight should be used with GA set up as web tracking due to use of URLs. Future plans include refactoring to work with GA set up for app-based tracking and the Measurement Protocol.

For debugging, Insight can track OS version, Node.js version, and version of the app that implements Insight. Please set up custom dimensions per below screenshot. This is a temporary solution until Insight is refactored into app-based tracking.

GA custom dimensions screenshot

Collected Data

Insight cares deeply about the security of your user's data and strives to be fully transparent with what it tracks. All data is sent via HTTPS secure connections. Insight provides API to offer an easy way for users to opt-out at any time.

Below is what Insight is capable of tracking. Individual implementation can choose to not track some items.

  • The version of the module that implements Insight
  • Module commands/events (e.g. install / search)
  • Name and version of packages involved with command used
  • Version of node.js & OS for developer debugging
  • A random & absolutely anonymous ID

Usage

Google Analytics

const Insight = require('insight');
const pkg = require('./package.json');

const insight = new Insight({
	// Google Analytics tracking code
	trackingCode: 'UA-XXXXXXXX-X',
	pkg
});

// Ask for permission the first time
if (insight.optOut === undefined) {
	insight.askPermission();
}

insight.track('foo', 'bar');
// Recorded in Analytics as `/foo/bar`

insight.trackEvent({
	category: 'eventCategory',
	action: 'eventAction',
	label: 'eventLabel',
	value: 'eventValue'
});
// Recorded in Analytics behavior/events section

Yandex.Metrica

const Insight = require('insight');
const pkg = require('./package.json');

const insight = new Insight({
	// Yandex.Metrica counter id
	trackingCode: 'XXXXXXXXX'
	trackingProvider: 'yandex',
	pkg
});

// Ask for permission the first time
if (insight.optOut === undefined) {
	insight.askPermission();
}

insight.track('foo', 'bar');
// Recorded in Yandex.Metrica as `http://<package-name>.insight/foo/bar`

API

Insight(options)

trackingCode

Required
Type: string

Your Google Analytics trackingCode or Yandex.Metrica counter id.

trackingProvider

Type: string
Default: 'google'
Values: 'google' | 'yandex'

Tracking provider to use.

pkg

Type: object

name

Required
Type: string

version

Type: string
Default: 'undefined'

config

Type: object
Default: An instance of conf

If you want to use your own configuration mechanism instead of the default conf-based one, you can provide an object that has to implement two synchronous methods:

  • get(key)
  • set(key, value)

Instance methods

.track(keyword, ...keyword?)

Accepts keywords which ends up as a path in Analytics.

.track('init', 'backbone') becomes /init/backbone

.trackEvent(options)

Accepts event category, action, label and value as described in the GA event tracking documentation via the options object. Note: Does not work with Yandex.Metrica.

.trackEvent({
	category: 'download',
	action: 'image',
	label: 'logo-image'
});
category

Required
Type: string

Event category: Typically the object that was interacted with (e.g. 'Video').

action

Required
Type: string

Event action: The type of interaction (e.g. 'play').

label

Type: string

Event label: Useful for categorizing events (e.g. 'Fall Campaign').

value

Type: integer

Event value: A numeric value associated with the event (e.g. 42).

.askPermission(message?)

Asks the user permission to opt-in to tracking and sets the optOut property in config. You can also choose to set optOut property in config manually.

askPermission screenshot

Optionally supply your own message. If message is null, default message will be used. This also resolves with the new value of optIn when the prompt is done and is useful for when you want to continue the execution while the prompt is running.

.optOut

Returns a boolean whether the user has opted out of tracking. Should preferably only be set by a user action, eg. a prompt.