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

@turbopasi/node-alarm

v0.0.5

Published

Trigger alarm based on event occurences

Downloads

4

Readme

node-alarm

node-alarm is a simple mechanism which can be plugged in almost everywhere in your code. Be it a button click, a request error, the results from a calculation or sensors. The "alarm" will be triggered whenever a certain event occurs too often within specified timeframe.

Example usage :

//alarm.js

const  Alarm  =  require('@turbopasi/node-alarm');
const  alarm  =  new  Alarm();

const  rule  = alarm.add({
	name :  "foo",
	maxEvents :  10,
	timeframe :  10000
});

// Listen for 'alarm' event directly on the rule, or
rule.on('alarm', () => {
	// Act on it
});

// listen globally for all rules
alarm.on('alarm', (rule) => {
	// Act on it
});

module.exports  = alarm;
// any.js

const  alarm  =  require('./alarm.js');

// Now, whenever an event occurs, which you want to keep track of,
// you raise the alarm buffer by 1.
webrequest.get("/notexist")
.catch(error => { 
	alarm.count("foo");
});

// If too many event like this occur (> maxEvents) within specified time (timeframe)
// the alarm will be raised.

// This should trigger the alarm
setInterval(() => {
	alarm.coun("foo");
}, 500)

// This shouldn't trigger the alarm
setInterval(() => {
	alarm.count("foo");
},2000)

Options

alarm.add( options );

While adding a new rule to your alarm stack you can specify the following options :

const options = {
	name		: 'unique-name', 
	/* Helps to identify rules after creating multiple rules */ 
	
	maxEvents	: 10,
	/* Maximum allowed amount of event occurences */ 
	
	timeframe	: 10000,
	/* Timeframe in milliseconds which within the maxEvents allowed to occur */ 
	
	autoreset	: false,
	/* If set to false, the alarm keeps triggering as long as conditions are met
	If set to true, the event count buffer clears onced triggered */
	
	once		: false
	/* If set to false, the alarm keeps triggering every time conditions are met,
	If set to true, the alarm triggers only once */ 
};