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

rubik-tasks

v2.3.0

Published

Task executor for Rubik

Downloads

7

Readme

Task executor for Rubik

Runs tasks delayed in time in Rubik's app.

Install

Via Yarn:

yarn add rubik-tasks

or NPM:

npm install rubik-tasks

Use

  1. Connect it to an app. Config and Log kubiks are required:
const path = require('path');
const { App, Kubiks } = require('rubik-main');
const Tasks = require('rubik-tasks');

const app = new App();
app.add([
  new Kubiks.Config(path.join(__dirname, './default/')),
  new Kubiks.Log,
  new Tasks(path.join(__dirname, './tasks/'))
]);

app.up().
then(() => {
  app.log.info('App is up');
}).
catch((err) => {
  app.log.error('App is down');
  app.log.error(err);
})
  1. Create tasks folder, and tasks within it tasks/myFirstTask.js
module.exports = {
  name: 'My first task',
  description: 'Just push message to logs time by time',
  time: '10:00',
  jobs: [function(tasks, app, task) {
    app.log.info('The texty text from', task.name);
  }]
};

Now when the application ups, the task ”My first“ task will be queued for execution at 10am.

Task options

  • id is an id of the task, it is not required, and used to manually stop the task;
  • name is a name of the task, it is not required;
  • description is a description of the task, it is not required;
  • time is a time of day, when the task should be started. Format is HH:mm;
  • period is the frequency in seconds when the task will be executed;
  • jobs is an array of functions, they are called one after another when the task is executed;
  • arguments is an array of additional variables for task's functions, they are they are placed at the beginning of the function arguments;
  • once is a flag to start task once;
  • context is a context of funtions inside jobs.

You can use placeholders for a period option:

  • 1w — a week;
  • 1d — a day;
  • 1h — a hour;
  • 1m - a minute.

Manualy add tasks

Just use add method:

tasks.add(task);

If you added a task before upping the app, then you no longer need to do anything.

If app is upped, you should start task manually:

const task = tasks.add(rawTask);
tasks.start(task);

Stop task

Just use stop method:

tasks.stop(taskId);