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

logsans

v0.0.10

Published

LogSans Client - LogSans is a companion library for LogSnag. LogSans enables notification for events that have NOT happened in a pre-defined frequency.

Readme

Installation

npm install --save logsans

Usage

Import Library

const {LogSnag} = require("logsans")

🕺 Notice how we've named the variable LogSnag (instead of the LogSans). This allows you to not have to change your exsiting code if you have already implemented LogSnag. 😎

Initialize Client

const logsnag = new LogSnag(process.env.YOUR_LOG_SNAG_TOKEN);

Publish Event & Track Event

logsnag.publish({
    project: "your-logsnag-project",
    channel: "your-logsnag-channel",
    event: "Your logsnag event",
    icon: "🎉",
    notify: true,
    logsans: true /* This property is only needed if you want LogSans to be able to notify you when this event does NOT happen. */
});

This will do two things:

  1. ✅ It publishes your event to LogSnag
  2. ✅ Tracks your event on LogSans so that LogSans can alert you when the event does NOT happen within the last X minutes. (X being the "frequency" set - more on that below)

Tell LogSans When to Check

Now that you are tracking your events, it is time to tell LogSans how often to check for it.

To do that, user the Create Recurring Check endpoint here:

logsnag.check({
    project: "your-logsnag-project",
    channel: "your-logsnag-channel",
    event: "Your logsnag event",
    frequency:20 /* in minutes */
});

More Documentation: https://documenter.getpostman.com/view/10930387/Uz5MFEMj

Once you create a Recurring Check, LogSans alert you if it has not detected your event in the timeframe set by the frequency property.

For Example

If frequency is set to 30 (minutes), LogSans will check every 30 minutes. If it does not detect your event, it will publish a LogSnag event telling you that it has not seen that event in the last 30 minutes.