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

gracenode-cron

v0.1.2

Published

cron module for gracenode module.

Downloads

1

Readme

gracenode-cron Module

Cron module for gracenode framework

This is designed to function within gracenode framework.

How to include it in my project

To add this package as your gracenode module, add the following to your package.json:

"dependencies": {
        "gracenode": "",
        "gracenode-cron": ""
}

To use this module in your application, add the following to your gracenode bootstrap code:

var gracenode = require('gracenode');
// this tells gracenode to load the module
gracenode.use('gracenode-cron');

To access the module:

// the prefix gracenode- will be removed automatically
gracenode.cron

##How to schedule a new task

In your config, make sure you have the schedule set for your task to run, for example:

    "modules:" {
		"cron": {
			"myCronJob": {
				"schedule": "*/30 * * * * *"
			}
		}
	}

On one of your machine, retrieve a Cron object like this:

var cron = gracenode.cron.create('myCronJob');

Next up you should add a callback to executed on each tick, if you're running a cluster of seperate nodes make sure that this is only executed on your master.

cron.addCallback(function() {
    console.log('I will show every 30 seconds!');
});

Finally, start the cronjob:

cron.start();

##Methods ###cron.create(name) Returns a new Cron object

var cron = gracenode.cron.create('myCronJob');

##Cron object ###constructor

var cron = new Cron('* * * * * *');

###cron.setTime(time) Set the time a cronjob should be executed, for example every 5 minutes:

cron.setTime('0 */5 * * * *');

###cron.addCallback(func) Add a callback to be executed on each tick

cron.addCallback(function () {
  console.log('I am executed on every tick!');
});

###cron.start() Start the cronjob, will executed a callback on every tick

cron.start();

###cron.stop() Stop the cronjob, will prevent each callback to be executed on every tick.

cron.stop();

###cron.getNextDate() Get a date object when the next tick will happen. The cronjob does not have to be running for this function to work.

var nextTick = cron.getNextDate();
console.log('Next tick will take place:', nextTick);

###cron.getSecondsRemaining() Get the seconds remaining until the next tick. The cronjob does not have to be running for this function to work.

console.log('The cronjob will execute in', cron.getSecondsRemaining(), 'seconds');