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

event-log

v2.1.6

Published

An append only event log with streaming support

Downloads

2

Readme

event-log

build status dependency status

An append only event log with streaming support

Example

An event-log is currently coupled to mongo and backed by two collection. A capped real time collection of events and a historic collection.

You configure the event log with a time to live, this means that the event log will keep events in memory for that period of time. If you try to read() from the log for any events older then Date.now() - timeToLive it will not return them.

The event log is designed for real time events and should be used in combination with snapshots, i.e. you read the recent state from a concrete snapshot and merge in real time data from the event log on the fly, preferably in the browser.

var eventLog = require("event-log")
var fold = require("reducers/fold")

/* get a mongoDB guy somehow */
var db = someMongoDb

db.createCollection("event-log.realtime", {
    capped: true
    , size: 100000
}, function (err, res) {
    /* ensure that the real time collection is capped */
    /* this allows us to use tailable cursors */
})

var realtimeCollection = db.collection("event-log.realtime")
var rawCollection = db.collection("event-log")

var log = eventLog(realtimeCollection, {
    timeToLive: 60 * 60 * 1000 /* HOUR */
    , rawCollection: rawCollection
})

/* each piece of data being added MUST have a timestamp */
log.add("event-type", {
    /* some data */
    timestamp: Date.now()
})

/* infinite stream of data */
var stream = log.read(Date.now() - 1000)

fold(stream, function (item) {
    /* item from event log */
})

Installation

npm install event-log

Contributors

  • Raynos

MIT Licenced