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

@vivareal/tracking

v3.0.7

Published

A set of tracking events helpers

Downloads

155

Readme

Tracking

A set of tracking helpers based on our schemas repository

Usage

// ../tracking.js
import { Tracking } from '@vivareal/tracking';

export default new Tracking({
  getBaseSchema: () => {
    // get info from base schema
    // ...
    return {
      foo: 'bar',
      bar: 'foo',
    };
  },
});

Options

| Option | default | Desc | | ------------- | ---------- | ---------------------------- | | getBaseSchema | () => {} | Get project base schema info |

Use as a Vue plugin

import Vue from 'vue';
import { VueTracking } from '@vivareal/tracking';
import tracking from './tracking';

Vue.use(VueTracking, { tracking });

This will enable your project to use the tracker directly in components in a "Vue-way"

import { favoriteClicked } from '@vivareal/tracking';

// foo.js
export default {
  methods: {
    trackEvent() {
      const schema = this.$tracking.getSchemaData(params, 'renameCollection', favoriteClicked);
      this.$clickstream.trackEvent(schema);
    },
  },
};

Use as module

// foo.js
import tracking from './tracking';
import { favoriteClicked } from '@vivareal/tracking';

const schema = tracking.getSchemaData(data, 'renameCollection', favoriteClicked);

Methods

| Method | Params | Desc | | ------------- | ------------------------------------------------- | --------------------- | | getSchemaData | data: obj, eventAction: String, schema: obj | Create desired schema |

// schema object example
{
  create: (event, data) => {
    const events = { myCustomEvent: { action: 'myCustomEvent' } };
    return { ...data, ...events[event] };
  },
  rules: {
    required: ['id', 'event'],
    event: 'myCustomEvent'
  }
}

Avaliable Schemas

| Event | Description | Used In | | ------------------------- | --------------------------------------------------------------------------------------- | ----------------------- | | favoritePanelClicked | Whenever the user open/closes the favorites modal | oz-assets, don-corleone | | favoriteClicked | whenever the user actually take an action on favarite modal | oz-assets, don-corleone | | favoriteCollectionClicked | whenever the user actually take an action on favorite modal of remove or add a favorite | oz-assets, don-corleone | | galleryClicked | whenever the user open/swipes a photo of gallery | oz-assets, don-corleone |

Run it locally

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Running on local machine

yarn dev

Running the tests

yarn test
yarn test:watch

Build

Build to dist folder

yarn run build

Code Formatting Guidelines

This project relies on prettier to automatically format the code. In the precommit hook, your code will be checked against eslint and prettier rules to avoid sending bad formatted code to production.

Publish a new version

See root's README file

Debug this module with Vscode

Vscode has some issues with debug in the newest version of ECMA Script. So we need to build first the module and call the functions with an entry point.

To debug create a .vscode folder and launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "skipFiles": ["<node_internals>/**"],
      "program": "${workspaceFolder}/dist/entry-point.js"
    }
  ]
}

And then build your package

yarn build

And now you call the modules inside on entry-point.js at dist folder. eg:

const { Tracking } = require('./tracking');
import { favoriteClicked } from '@vivareal/tracking';

const data = {
 ...
};

const tracking = new Tracking({
  getBaseSchema: () => {
    // ..
  },
 });

tracking.getSchemaData(data, 'renameCollection', favoriteClicked);