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

@ridi/ridi-event-tracker

v0.1.3

Published

[![npm](https://img.shields.io/npm/v/@ridi/ridi-event-tracker.svg)](https://www.npmjs.com/package/@ridi/ridi-event-tracker)

Downloads

6

Readme

@ridi/ridi-event-tracker

npm

Provides tracking API that helps to send events to various logging services like Google Analytics, RIDI beacon system

Install

NPM

$ npm install @ridi/ridi-event-tracker

Browser

# local
<script src="./node_modules/@ridi/event-tracker/dist/umd/bundle.min.js"></script>

# In GTM
<script src="https://unpkg.com/@ridi/ridi-event-tracker@{{EVENT_TRACKER_VERSION}}/dist/umd/bundle.min.js"></script>
<script>
  var beaconSrc = 'https://s3.ap-northeast-2.amazonaws.com/beacon-ridibooks-2/beacon_ridibooks_2.gif';
  window.ret = new Tracker({
    deviceType: '{{DeviceType}}',
    uId: '{{UserID}}',
    beaconOptions: {
      beaconSrc: beaconSrc
    }
  });
  window.ret.initialize();
</script>

Usage

import { Tracker, DeviceType } from "@ridi/event-tracker";

const tracker = new Tracker({
  deviceType: DeviceType.PC,
  uId: 123456,
  debug: false,
  throttleWait: 1000,
  beaconOptions: {
    beaconSrc: "http://beacon.com",
  },

});

tracker.initialize();

tracker.sendPageView(location.href);

tracker.sendEvent("Purchased", {
  t_id: "201808180210135",
  value: 29000
});

API

new Tracker(MainTrackerOptions)

MainTrackerOptions

| Key | Required | Type | Description | | ------------------------------ | -------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | debug | false | boolean | Defaults to false If set to true, All fired events are logged to browser via console.log | | uId | false | number | Logged user's identifier. | | deviceType | true | DeviceType | Type of connected user's device. Please refer DeviceType type | | Additional properties related to specific service. Please refer ServiceProp type, which is Record<string, string> | | beaconOptions | false | BeaconOptions | Options related with Beacon tracking module | | beaconOptions.beaconSrc | false | string | Source of the image to be used as a beacon | | ID of impression event tag

Tracker.initialize()

To use this library correctly, you need to call this method least once either before calling other methods or after.

written event records before calling initialize, this records flush after initialized.

Develop

$ git clone https://github.com/ridi/event-tracker && cd tracking
$ npm install
$ npm run build

Test

$ npm run test

Publish

$ npm login
$ npm run deploy
$ # or
$ npm run build && npm publish --access public

LICENSE

MIT