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

count-interval

v1.0.1

Published

setInterval replacement that only fires a fixed number of times

Downloads

640

Readme

countInterval

A version of setInterval that automatically terminates after count runs. A single parameter count is added after the normal milliseconds parameter, and before any other passed parameters. The code is kept to a minimal footprint.

Installation

$ npm i -S count-interval

or

$ yarn add count-interval

Usage

Basic example:

const countInterval = require('./countInterval');

const timer = countInterval(() => {
  console.log('fired!', new Date());
}, 1000, 3);

Outputs:

fired! 2019-05-03T16:15:31.582Z
fired! 2019-05-03T16:15:32.584Z
fired! 2019-05-03T16:15:33.586Z

Same example, passing a parameter to the setInterval function:

const countInterval = require('./countInterval');

const timer = countInterval(text => {
  console.log(text, new Date());
}, 1000, 3, 'fired!');

This outputs the same as above.

You can kill the setInterval just like normal.

const timer = countInterval(text => {
  console.log(text, new Date());
}, 1000, 3, 'fired!');

clearInterval(timer)

This will stop the timer before it fire, so there's no output.

Test

To keep things light, there's a test, but it only logs to console.

$ npm test

This outputs something like:

test 2019-05-03T16:19:19.114Z 1
test 2019-05-03T16:19:19.218Z 2
test 2019-05-03T16:19:19.321Z 3
test 2019-05-03T16:19:19.422Z 4
test 2019-05-03T16:19:19.525Z 5
test 2019-05-03T16:19:19.628Z 6
test 2019-05-03T16:19:19.732Z 7
test 2019-05-03T16:19:19.835Z 8
test 2019-05-03T16:19:19.936Z 9
test 2019-05-03T16:19:20.037Z 10