Originally this project was a NodeJS fork of James Padolsey's cron.js.
After Craig Condon made some updates and changes to the code base this has evolved to something that has a bit of both. The cron syntax parsing is mostly James' while using timeout instead of interval is Craig's.
Additionally, this library goes beyond the basic cron syntax and allows you to supply a Date object. This will be used as the trigger for your callback. Cron syntax is still an acceptable CronTime format. Although the Cron patterns suported here extend on the standard Unix format to support seconds digits, leaving it off will default to 0 and match the Unix behavior.
Because we can't magically know what you are doing to expose an issue, it is best if you provide a snippet of code. This snippet need not include your secret sauce, but it must replicate the issue you are describing. The issues that get closed without resolution tend to be the ones without code examples. Thanks.
As goes with semver, breaking backwards compatibility should be explicit in the versioning of your library. As such, we'll upgrade the version of this module in accordance with breaking changes (I'm not always great about doing it this way so if you notice that there are breaking changes that haven't been bumped appropriately please let me know). This table lists out the issues which were the reason for the break in backward compatibility.
| Node Cron Ver | Issue # |
| 1.0.0 |
var cronJob = require('cron').CronJob;
new cronJob('* * * * * *', function(){
console.log('You will see this message every second');
}, null, true, "America/Los_Angeles");
Asterisk. E.g. *
Ranges. E.g. 1-3,5
Steps. E.g. */2
Read up on cron patterns here.
var cronJob = require('cron').CronJob;
var job = new cronJob('00 30 11 * * 1-5', function(){
// Runs every weekday (Monday through Friday)
// at 11:30:00 AM. It does not run on Saturday
// or Sunday.
}, function () {
// This function is executed when the job stops
},
true /* Start the job right now */,
timeZone /* Time zone of this job. */
);
var cronJob = require('cron').CronJob;
var job = new cronJob(new Date(), function(){
//runs once at the specified date.
}, function () {
// This function is executed when the job stops
},
true /* Start the job right now */,
timeZone /* Time zone of this job. */
);
var cronJob = require('cron').CronJob;
var job = new cronJob({
cronTime: '00 30 11 * * 1-5',
onTick: function() {
// Runs every weekday (Monday through Friday)
// at 11:30:00 AM. It does not run on Saturday
// or Sunday.
},
start: false,
timeZone: "America/Los_Angeles"
});
job.start();
try {
new cronJob('invalid cron pattern', function() {
console.log('this should not be printed');
})
} catch(ex) {
console.log("cron pattern not valid");
}
From source: `npm install`
From npm: `npm install cron`
If you want to specify timezones, you'll need to install the time module or place an entry for it in your package.json file.
npm install time
Parameter Based
CronJob
constructor(cronTime, onTick, onComplete, start, timezone, context)- Of note, the first parameter here can be a JSON object that has the below names and associated types (see examples above).cronTime- [REQUIRED] - The time to fire off your job. This can be in the form of cron syntax or a JS Date object.onTick- [REQUIRED] - The function to fire at the specified time.onComplete- [OPTIONAL] - A function that will fire when the job is complete, when it is stopped.start- [OPTIONAL] - Specifies whether to start the job after just before exiting the constructor.timeZone- [OPTIONAL] - Specify the timezone for the execution. This will modify the actual time relative to your timezone.context- [OPTIONAL] - The context within which to execute the onTick method. This defaults to the cronjob itself allowing you to callthis.stop(). However, if you change this you'll have access to the functions and values within your context object.
start- Runs your job.stop- Stops your job.
CronTime
constructor(time)time- [REQUIRED] - The time to fire off your job. This can be in the form of cron syntax or a JS Date object.
MIT