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

node-red-contrib-looptimer2

v0.0.2

Published

Sends msg to the first output continually, once per specified time, till a msg with any topic of 'stop' or 'STOP' is received on input.

Downloads

202

Readme

Loop Timer 2 for node-red

This node fixes a loop timer node problem. When you send "stop" as an msg string to the node and then run the loop again, it will execute as expected, unlike the original node.

Sends the msg through the first output, then continues to do so in a loop, once per the timer duration specified, until a payload of stop or STOP is received, at which time the second output will automatically send a payload of stopped.

Sends msg to the first output continually, once per specified time, till a msg with any topic of stop or STOP is received, at which time the second output will automatically send a payload of stopped.

You can also stop the loop by specifying a maximum number of loops, which when reached, will stop the loop and timer, as well as sending a payload of max loops reached through the second output. Keep in mind, the first msg simply passes through, and is therefore not part of the loop. So if you set the max loops to 5, you will get 6 messages, which is 1 original message, and 5 messages from the loop.

Finally, to ensure you do not end up with an infinite loop, you can set a maximum timeout in seconds, minutes or hours, and when that time is reached, the loop and timer will also be stopped.

Setting the Max Loops and Max Timeout settings to high values can, for all intents, ensure that the loop can only be stopped by an incoming stop payload, however, the stability of the loop has not been tested over an extended number of hours.