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 🙏

© 2025 – Pkg Stats / Ryan Hefner

after-every

v1.0.4

Published

Run a function after every second/minute/hour...

Readme

after-every

This package allows you to run a function after a time interval of seconds, minutes, hours or days. The function is created to run after the time in millisecond becomes 0. For example, the seconds will run after the time in milliseconds becomes 0. The minute function will run after the time in seconds becomes 0, and so on.

This is useful for projects that need to run a function as the second or minute changes.

Installation & Importing

npm install after-every

or

yarn add after-every

then import the module like either of the two ways below depending on your project

// Import statements
import AfterEvery from "after-every"

// Require statements
const AfterEvery = require("after-every").default

Usage

To create a timer that runs every 5 minutes, all I have to do is this

AfterEvery(5).minutes(date => {
	console.log("I run every 5 minutes")
}) 

It works the same way for all other time durations

AfterEvery(1).seconds(date => {})
AfterEvery(5).minutes(date => {})
AfterEvery(10).hours(date => {})
AfterEvery(7).days(date => {})

To clear the timeout, just call the function again

const timer = AfterEvery(1).seconds(date => console.log(`A second passed!, now it's ${date.getSeconds()} seconds`))
setTimeout(() => {
	timer()
}, 3000)

// > Output
// A second passed! now it's 1 seconds
// A second passed! now it's 2 seconds
// A second passed! now it's 3 seconds

Fixing AfterEvery().days() with set_timezone()

AfterEvery().days() runs every time UTC hours strikes 0. Since the timezone your run your code in might be different from that of UTC, there is a function for your to set your custom timezone so that AfterEvery().days() runs when your timezone days starts

import { set_timezone } from "after-every"

set_timezone(8)  // For UTC+08:00
set_timezone(-3) // For UTC-03:00