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 🙏

© 2025 – Pkg Stats / Ryan Hefner

left-hook-analytics-client

v0.0.7

Published

Client package for programmatically leveraging the left-hook-analytics api

Downloads

13

Readme

left-hook-analytics-client

Client package for programmatically leveraging the left-hook-analytics api

Usage

To use this package, you must first obtain an Application API Key from the Left Hook Analytics administrator.

Create an instance of the left hook analytics client using your Application Api Key

const AnalyticsClient = require("left-hook-analytics-client")

let analytics = new AnalyticsClient({
   applicationApiKey : "my-application-api-key"
})

Assuming you have provided a valid Application API Key, the client will now fetch your service-level keys. This should occur rather quickly after instantiation, so you are unlikely to leverage client methods before this information has been retrieved. However, service-level api calls will await service-level key retrieval before making any requests. If you have provided an invalid Application API Key, attempting to leverage service methods will throw an error.

Once application details have been fetched, log service methods will be exposed.

Error Logging

To report an error to the Left Hook Analytics API, use the logError method available on the AnalyticsClient instance. Every log method expects a manifest object. The shape of a manifest varies for each log type. An error manifest must have the string properties attempt and origin, and may optionally include a stack and meta property, either of which may be a string, number, object, or array.

async function mightFail ( myParam ){
   let someParam = myParam
   try {
      // ...
      let result = await someAsyncOperation(someParam)
      // ...
      return result
   } catch(err){
      console.error(err)
      analytics.logError({
         origin : "myFile.js",
         attempt: "someAsyncOperation",
         stack : err,
         meta : {
            someParam : myParam
         }
      })
   }
}

The logError method has no return value, and is treated in code as a synchronous function. Assuming the Application API Key you have provided is valid and the origin and attempt properties have been given literal values, it is guaranteed that your log has been recorded. When an error log is recorded, the application name and the application id are associated with that log, so that you may retrieve aggregate statistics and application-related details at a later time.