Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

recron

Package Overview
Dependencies
Maintainers
1
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

recron

Simple, intuitive and readable cron implementaiton

  • 1.1.6
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

Recron

CI status

Recron is a simple, intuitive and readable cron implementaiton written in TypeScript and suitable for Node.js and browser usage.

Highlights

  • Object oriented design.
  • Support update schedule on the fly.
  • Support both crontab and interval syntax.
  • Support multi-timezone in a single cron object.
  • Tickless scheduler (will be optional in feature).
  • Compact and quite readable code base written in TypeScript.

Usage

import { Cron } from 'recron';

const cron = new Cron();

// Start cron scheduler.
cron.start();

// Use interval syntax.
cron.schedule('@every 1s', () => {
  console.log('every second', new Date());
});

// Use crontab syntax.
cron.schedule('*/5 * * * * *', () => {
  console.log('at 5th second', new Date());
});

// Stop cron after 10 seconds.
cron.schedule(
  '@every 10s',
  () => {
    cron.stop();
    console.log('done', new Date());
  },
  { oneshot: true }
);

Timezone

The constructor of Cron takes an optional parameter as its default timezone. If the timezone parameter unspecified, the default timezone will be detected from Intl.DateTimeFormat, it will be your local timezone in general. Mean while, the last parameter of schedule() method options has an optional timezone property, which can be used to override the default timezone.

Note: timezone only affects cron syntax and its alias, interval syntax has nothing to do with timezone.

Reentrant

Unlike other cron implementations, reentrant is not allowd in recron by default for both safe and convenient. Therefore, if a handler take a lot of time to process, it will underrun. For example, given following piece of code:

const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));

cron.schedule('@every 1s', async () => {
  console.log('overslept', new Date());
  await sleep(3000);
});

the output will be:

overslept 2019-10-31T05:05:27.251Z
overslept 2019-10-31T05:05:30.253Z
overslept 2019-10-31T05:05:34.254Z
overslept 2019-10-31T05:05:37.263Z
overslept 2019-10-31T05:05:40.275Z

To disable this feature, set reentrant to true in options. But be careful, if the providered handler always underrun, due to a lot of unresolved promises, the memory consumption will keep increasing, and eventually you program will run OOM.

Crontab Alias

recron has following crontab aliases:

AliasCrontab
@hourly0 * * * *
@daily0 0 * * *
@weekly0 0 * * 1
@monthly0 0 1 * *

Note: we use Monday as the first day of the week according to international standard ISO 8601. So @weekly means "at 00:00 on Monday", not Sunday.

Interval Syntax

Interval syntax has following specifiers:

OrderSpecifierUnit
1hhour
2mminute
3ssecond
4msMillisecond

One ore more specifiers can be used, as long as they are arranged in ascending order:

  • @every 10s
  • @every 30m
  • @every 1h30m

Keywords

FAQs

Package last updated on 09 May 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc