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

time-buffer

v0.0.1

Published

Second granularity for time-sensitve averages

Downloads

3

Readme

time-buffer Build Status

Storing per-second granularity data in a standard circular buffer leaves old values in place if there is nothing collected. This can lead to the illusion of newly arrived data when in fact there has simply been nothing to overwrite the buffer. The possible solutions are a 'reaper' thread/interval that clears out old buffers or a queue of values from which old values are removed. This library takes the latter approach through it may eventually support both. Here is an example:

var TimeBuffer = require('time-buffer');

// Create 3 buffers of different durations
var bufferFiveSec = new TimeBuffer(5);
var bufferOneMin = new TimeBuffer(60);
var bufferTwoMin = new TimeBuffer(120);

var interval = setInterval(function() {
	var rand = Math.floor(Math.random() * 10);
	bufferFiveSec.add(rand);
	bufferOneMin.add(rand);
	bufferTwoMin.add(rand);
	console.log(bufferFiveSec);
	console.log(bufferOneMin);
	console.log(bufferTwoMin);
}, 2000); // Even at 2 seconds this works. We time-buffer handles the gaps correctly.