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

@danieldiekmeier/async-worker

v2.0.0

Published

A simple worker to do work in intervals

Downloads

7

Readme

Async Worker

npm i @danieldiekmeier/async-worker

Usage

Do you have a task that needs to run every now and then? Do you not want to worry about setting up a cronjob, but also not just slap a setInterval on it and call it a day? Then this package is the middle ground for you.

Put your worker logic somewhere in your application logic, reuse all your stuff, it's going to be fine!

✨ async/await is fully supported and encouraged ✨

Here is a code example:

import Worker from '@danieldiekmeier/async-worker'

new Worker({
  // This function is called on every task execution.
  async task () {
    await database.removeOldStuff()
  },

  // Set the minimum time between task executions, in milliseconds (ms).
  // In this case, it would run once per hour.
  interval: 60 * 60 * 1000,

  // Whenever the task errors, this function is called with the error.
  onError (err) {
    fancyLogger(err)
  }
})

The Worker doesn't start the task if the previous execution is still running. That way, you don't have to worry about having long running tasks like complex database cleanup or slow download tasks.