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

@marianmeres/ticker

v1.14.0

Published

Do something when it ticks.

Downloads

21

Readme

@marianmeres/ticker

Do something when it ticks. With a store compatible API.

Under the hood it uses recursive setTimeout with interval corrections, so it should guarantee the precise frequency except for the edge cases where the synchronous subscriber's work cannot keep up with the interval - it will never tick sooner before it finishes.

Install

$ npm i @marianmeres/ticker

Usage

import { createTicker } from '@marianmeres/ticker';

// once started, will tick every 1000 milliseconds
// (interval = 1000, start = false): Ticker
const t = createTicker(1_000);

// basic control api
t.start();
t.stop();

// decrease/increase frequency on existing instance
t.setInterval(ms);

// subscribe api
const unsub = t.subscribe((timestamp) => {
	if (timestamp) {
		// do something on tick
	} else {
		// ticker is stopped (or has not started yet)
	}
});

Delayed Worker Ticker

Using a tick signal from a sync ticker shown above for a periodical asynchronous work (e.g. periodical api data fetching) may not be the best choice. For such cases, use its "delayed" sibling. Instead of frequency, it guarantees a delay between worker calls.

Delayed Worker Ticker Usage

import { createDelayedWorkerTicker } from '@marianmeres/ticker';

// once started, it will do the work, then pause for 1 second, then repeat...
// (worker: CallableFunction, interval = 1000, start = false): DelayedWorkerTicker
const t = createDelayedWorkerTicker(async () => fetch('/api'), 1_000);

// control api
t.start();
t.stop();
t.setInterval(ms);

// subscribe api
const unsub = t.subscribe(({ started, finished, error, result }) => {
	// both `started` and `finished` are timestamps (or zero)
	if (started && !finished) {
		// worker's work is in progress
	} else if (started && finished) {
		// do something with `result` or `error`
	} else {
		// ticker is stopped (or has not started yet)
	}
});

Interval value as a function

If desired, you can define the interval value as a function which returns the number of ms.

type Interval = number | ((previous: number) => number);