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-rate

v1.0.0

Published

A library designed to calculate time rates of events in real-time.

Downloads

2

Readme

time-rate

A simple library to measure time rates. Uses Luxon under the hood.

Usage

Simplest case, defaults to 10-second windows, returns numbers in rate per second.

import * as TimeRate from 'time-rate';

TimeRate.init({ key: 'heartbeat' });

setInterval(() => {
    TimeRate.register('heartbeat');
    console.log(`Heart is beating at ${TimeRate.rate('heartbeat')} beats per second.`);
}, 500);

Or you can customize it:

import * as TimeRate from 'time-rate';

TimeRate.init({ key: 'heartbeat', ratePer: 'minute', windowLength: 1, windowUnit: 'minute' });

setInterval(() => {
    TimeRate.register('heartbeat');
    console.log(`Heart is beating at ${TimeRate.rate('heartbeat')} beats per minute.`);
}, 2000);

Discrete Mode

Defaults to discrete mode. This is faster and uses less memory. Keeps track of the number of events per window. However your rate results will not be instantaneous, you will get the rate for the previous window. Keep windows smaller if you want more up-to-date results.

import * as TimeRate from 'time-rate';

TimeRate.init({ key: 'heartbeat', ratePer: 'minute', mode: 'discrete', windowLength: 10, windowUnit: 'seconds' });

setInterval(() => {
    TimeRate.register('heartbeat');
    console.log(`Heart is beating at ${TimeRate.rate('heartbeat')} beats per minute.`);
}, 2000);

Rolling Mode

This keeps track of every event that has fired during the specified window. Erases events once they are past the window. Gives the most accurate value, but at the cost of storage space and speed.

import * as TimeRate from 'time-rate';

TimeRate.init({ key: 'heartbeat', ratePer: 'minute', mode: 'rolling', windowLength: 1, windowUnit: 'minute' });

setInterval(() => {
    TimeRate.register('heartbeat');
    console.log(`Heart is beating at ${TimeRate.rate('heartbeat')} beats per minute.`);
}, 2000);

If you register 50,000 events per minute and your window is 1 minute, then an array of 50,000 dates is allocated. Use this mode only if you know you're okay with that tradeoff.