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

@unicornsprings/track-client-sdk-js

v0.1.1

Published

Client library for track service

Downloads

1

Readme

Track Client SDK

A client SDK that enables the application to submit user actions to the track service.

If you are using the track proxy, you should configure the proxy to include the a header with an account id (for example, Track-Account-Id, or any other other authorization header like Authorization: Bearer <access_token>) on all track requests, so you don't have to configure the track SDK with any account-specific information. You can then configure separate account id's in production and development environments using the track proxy, without having to customize the Track Client SDK configuration for each deployment.

If you are not using the track proxy, and you need to send a header with the track requests indicating an account id or access token, you can include it in the requestHeaders parameter when you initialize the client, like this:

const track = new TrackClient({
    serviceEndpoint: '/track',
    requestHeaders: {
        'Track-Account-Id': '<account_id>',
    },
});

API

You can use async/await:

async function example() {
    await this.$track.event({ action: 'signup' });
    // do the next thing after event is recorded
}

You can use then():

function example() {
    this.$track.event({ action: 'signup' })
        .then(result => { /* do the next thing after event is recorded */ })
        .catch(error => { /* handle error */ });
}

You can send the event and continue without waiting for it:

function example() {
    this.$track.event({ action: 'signup' });
    // do the next thing immediately without waiting
}

Vue

Add this to main.js, or anywhere you configure the track sdk:

import { TrackClient } from '@unicornsprings/track-client-sdk-js';
...
Vue.prototype.$track = new TrackClient({ serviceEndpoint: '/track' });

To configure the track client to send an event on every route change, add this to your App.vue file so it applies to all pages. Alternatively, you can add it to every page where you want to add tracking.

The event info object is completely arbitrary -- send whatever you want to see in the campaign manager. The track SDK already sends the complete URL from window.location.href with each event so you don't have to send route info unless it's more convenient for you to parse out a specific query parameter here and send it separately.

Note that we are NOT waiting for this request to complete, so we don't hold up the UI.

    watch: {
        $route(to) {
            this.$track.event({ action: 'route' });
        },
    },

Gridsome

Add this to main.js, or anywhere you configure the track sdk:

import { TrackClient } from '@unicornsprings/track-client-sdk-js';
...
Vue.prototype.$track = new TrackClient({ serviceEndpoint: '/track' });

To configure the track client to send an event on every route change, add this to your App.vue file so it applies to all pages. Alternatively, you can add it to every page where you want to add tracking.

Note the use of process.isClient to ensure we only track events by visitors, and don't call the track API when we're generating static pages before deployment. For more information, see gridsome docs.

    watch: {
        '$route.path': function onChangeRoutePath(newVal) {
            if (process.isClient) {
              this.$track.event({ action: 'route' });
            }
        },
    },
    mounted() {
        if (process.isClient) {
          this.$track.event({ action: 'route' });
        }
    },