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

q3-core-scheduler

v4.5.16

Published

For handling background processes in your application use Q3 Scheduler. We recommended running the scheduler on an independent server since it uses MongoDB as a persistence layer. This way, your web requests and your jobs don't need to compete for res

Downloads

307

Readme

Scheduler

For handling background processes in your application use Q3 Scheduler. We recommended running the scheduler on an independent server since it uses MongoDB as a persistence layer. This way, your web requests and your jobs don't need to compete for resources.

Scheduler.queue

To add one-time jobs, call the queue method. It takes two arguments: the name and the payload (optional). The payload can contain any data, though it will process the buckets and session properties differently.

If the payload contains buckets, the receiving function will have file attachments in its second parameter position. Likewise, if the payload contains session, it will hydrate the q3-core-session module before executing the file.

const Scheduler = require('q3-core-scheduler');

Scheduler.queue('file', {
  buckets: [],
  session: {},
  id: 1,
}).then(() => {
  // will eventually call the file below at chores/file.js
});

module.exports = (data, attachments) => {
  console.log('Regular data:', data);
  console.log('File buffers:', attachments);
};

Scheduler.seed

When the scheduler receives a target directory, it will walk the files in it looking for recurring jobs. Recurring jobs have files ending in @${interval}.js. Acceptable interval values include annually, biannually, quarterly, monthly, weekly, daily, bihourly, hourly, semihourly, biminutely and minutely.

const Scheduler = require('q3-core-scheduler');

// tells the scheduler to look for jobs in this directory
Scheduler.seed(__dirname).then(() => {
  console.log('Recurring jobs saved');
});

Scheduler.start

Given an executable directory and an interval, the queue manager can run. It will work by priority sequence (high to low) and lock any jobs in progress, processing just one at a time. After execution, the queue manager will stamp a completition date (iso) and duration (ms) for benchmarking and debugging purposes.

const Scheduler = require('q3-core-scheduler');

// tells the scheduler to execute files in this directory
// every 10 milliseconds
Scheduler.start(__dirname, 10).then(() => {
  console.log('Queue manager started');
});

Events

Scheduler implements a custom EventEmitter and exposes its on listener publicly. During the queueing process, each job will emit two of three events.

  1. Scheduler.on("start"): Every job emits this event before it executes;
  2. Scheduler.on("finish"): Successful jobs emit this event before the queue starts to look for the next job;
  3. Scheduler.on("stall"): Failed jobs emit this when an error occurs during execution.

Alternatively, when a new job gets added, the emitter will fire the queued event.