A Node cron wrapper to run your tasks even if their running time is gone
npm install node-cron-trigger shell
$ npm i node-cron-trigger
`
Using yarn:
` shell
$ yarn add node-cron-trigger
`
Summary
- Node-Cron is a perfect option to schedule tasks on server side to run in a specific time of the day but what if your task is should run at 12.00 AM and the server stopped at 11.59 PM and starts again at 12.01 AM that's mean your cron task won't run again untill the next day so here we need a solution to handle those expaired tasks at any app that's what Node-Cron-Trigger does it will combine node-cron with node-parser to save your tasks data in a file called history.log that will save your cron tasks by names in object and each key consist of object that have 2 keys createdAt and nextRunDate so whenever the server restart it will check for the tasks that need to get run if their nextRunDate is passed or not and if they are is passed then it will run them and update it's nextRunDate property that will happens just with expaired tasks but if the task run without any problems it's will never do anything it will just update that task nextRunDate property and keep going that's the process and let's go in details
Usage
- Node-Cron-Trigger lets you define the tasks as an object of keys - the key = the task name and the value is an object with 3 options
__schedule:__ the cron expression like *
* __options:__ node-cron schedule options you can find it in the following url Schedule Options
* __task:__ your task handler
- NodeCronTrigger accepts 2 arguments first one start as descriped above and optional options argument which is an object that object allows you to specify your custom store instead of default filesystem store or the filesystem history.log file path, name like new NodeCronTrigger({ historyFilePath: process.cwd(), historyFileName: 'tasks.log' }) or new NodeCronTrigger({ store: new MyCustomStore() })
$3
- logging boolean, default is true (allows you to disable logging)
- store: IStore, default is FileStore instance allows you to provide your own store to use it instead of default FileStore
- historyFilePath: path to the history, this field is required when you are not providing a store it will require you to provide a path to the history file
- historyFileName: allows you to change the history file name from history.log to any name you want
- Usage example ESM
` javascript
import { NodeCronTrigger, ITaskOptions, ITaskOptionsList } from "node-cron-trigger";
const options: ITaskOptionsList = {
historyFilePath: __dirname,
logging: true,
};
const tasks: ITaskOptions = {
"runAt12AM": {
schedule: '0 0 0 *',
options: {
scheduled: true,
},
task() {
console.log('hey whatever you did i will run at 12 AM even after restarting the server');
},
},
"runEach1Mins": {
schedule: '/1 *',
task() {
console.log('hey whatever you did i will run each 1 minutes of any hour even after restarting the server');
},
},
};
const runner = new NodeCronTrigger(tasks);
// get list of { tasks, scheduledTasks, cronTasks }
console.log(runner.getJobs());
// get the tasks history object
console.log(runner.getHistory());
// Error: Invalid expression
console.log(runner.validate('* 4'));
// get history file path
console.log(runner.historyPath);
setTimeout(() => {
console.log(runner.Tasks);
runner.store.getItem('history').then(history => console.log(JSON.parse(history), '............ history ..............'));
}, 1000 * 2);
`
- Usage example CJS
` js
const { NodeCronTrigger } = require('node-cron-trigger');
new NodeCronTrigger(
{
runEach1Mins: {
schedule: '/1 *',
task() {
console.log(
'hey whatever you did i will run each 1 minutes of any hour even after restarting the server'
);
}
}
},
{
historyFilePath: __dirname,
logging: false
}
);
`
Store
- storing data by Node-Cron-Trigger can made by any data store like databases or redis store or anything else by default it's using FileStore to store the history in log file but also you have the free to use your favorite data store but keep in mind that any data store is should provide 3 methods setItem which take the data as key, value like localStorage in browser + getItem which take the key as argument + removeItem which also take key as an argument and each one of them is should return a promise to handle any type of data storage you can checkout the example you can show it in Store.ts file
- in that store all data will be save as json string in key called history so if you planning to store history in a pre defined store like SQL you will need to define the history key as a string type like nvarchar(max)
Methods
- because of node-cron-trigger is a cron wrapper you can use any node-cron method and options beside the node-cron-trigger default usage described above you can also use a method like schedule, validate, getTasks of node-cron check node-cron docs
- Also 4 more options like
* getHistory which return your tasks object that referred here you can use it like new NodeCronTrigger(tasks).getHistory()
getTaskNextRunTime that's will take the cron expression as argument and it will return the date of the task next run date it's just a funny method to checkout your cron expression next run date you can try it like console.log(new NodeCronTrigger(tasks).getTaskNextRunTime('/5 '))
* clearHistory that will remove the node-cron-trigger history - it's a cleanup method that can be used when you change you cron tasks because of node-cron-trigger will persist any defined tasks even if they removed their data will still exists for example if you was have 3 tasks like runEach1Mins, runEach2Mins, runEach3Mins and removed the task of runEach1Mins from your object in node-cron-trigger the data of runEach1Mins will stay exists so you can use it to remove the old tasks data and it will automatically create a new history with presented cron jobs that method won't effect any of your tasks whatever the tasks data exists or removed because only defined tasks will run
History
- Node-Cron-Trigger history by default it's a log file that consist of object with one key history which is a json string contains the data for your tasks - the tasks is saved in the json data as an object like tasks-names and each task-name is an object with 2 keys createdAt and nextRunDate the file will looks like
` json
{
"runAt12AM": {
"createdAt": "2024-03-12T02:49:23.536Z",
"nextRunDate": "2024-03-12T22:00:00.000Z"
},
"runEach1Mins": {
"createdAt": "2024-03-12T02:49:23.563Z",
"nextRunDate": "2024-03-12T02:53:00.000Z"
}
}
``