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

lastseen

v0.0.0

Published

track when things were last seen

Downloads

52

Readme

lastseen

Track when users/things were last seen using redis.

This library is pretty experimental right now but does actually work, I'm just not sure how much of a good idea it is

CAUTION - HERE LIE DRAGONS FOR THE UNWARY

Unlike some other "who is online" libraries which you might come across, this library does not expire keys (it can't because of Redis' current design) and is therefore unbounded in terms of memory consumption. If you keep on tracking new ids you will eventually run out of RAM.

This is completely by design, it's meant to track things for very long periods of time.

Installation

$ npm install online

Example

var Lastseen = require('lastseen');
var redis = require('redis');
var client = redis.createClient()

var opts = {
  redisKey: 'online' //name for redis key for set
}

var lastseen = Lastseen(client, opts);


lastseen.add(someId, function(err){
  //optional callback fired when written to redis
})

//Check if a user is known about
lastseen.find(someId, function(err, result){
  //err if redis failure
  //result is null for not known, or last seen timestamp for user
})

Usage

For now read the docblocks in index.js

TODO

EVERYTHING

PRs, issues bugs, comments and general derision are welcome

  • moar tests, the current tests folder has alot of left over stuff from previous APIs
  • functions to remove ranges (remove old entries by number/time)maybe expensive
  • some kind of benchmarking to see what it's any good at