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

@xen-orchestra/cron

v1.0.6

Published

Focused, well maintained, cron parser/scheduler

Downloads

53

Readme

@xen-orchestra/cron Build Status

Focused, well maintained, cron parser/scheduler

Install

Installation of the npm package:

> npm install --save @xen-orchestra/cron

Pattern syntax

<minute> <hour> <day of month> <month> <day of week>

Each entry can be:

  • a single value
  • a range (0-23 or */2)
  • a list of values/ranges (1,8-12)

A wildcard (*) can be used as a shortcut for the whole range (first-last).

Step values can be used in conjunctions with ranges. For instance, 1-7/2 is the same as 1,3,5,7.

| Field | Allowed values | |------------------|----------------| | minute | 0-59 | | hour | 0-23 | | day of the month | 1-31 or 3-letter names (jan, feb, …) | | month | 0-11 | | day of week | 0-7 (0 and 7 both mean Sunday) or 3-letter names (mon, tue, …) |

Note: the month range is 0-11 to be compatible with cron, it does not appear to be very standard though.

API

createSchedule(pattern: string, zone: string = 'utc'): Schedule

Create a new schedule.

  • pattern: the pattern to use, see the syntax
  • zone: the timezone to use, use 'local' for the local timezone
import { createSchedule } from '@xen-orchestra/cron'

const schedule = createSchedule('0 0 * * sun', 'America/New_York')

Schedule#createJob(fn: Function): Job

Create a new job from this schedule.

  • fn: function to execute, if it returns a promise, it will be awaited before scheduling the next run.
const job = schedule.createJob(() => {
  console.log(new Date())
})

Schedule#next(n: number): Array<Date>

Returns the next dates matching this schedule.

  • n: number of dates to return
schedule.next(2)
// [ 2018-02-11T05:00:00.000Z, 2018-02-18T05:00:00.000Z ]

Schedule#startJob(fn: Function): () => void

Start a new job from this schedule and return a function to stop it.

  • fn: function to execute, if it returns a promise, it will be awaited before scheduling the next run.
const stopJob = schedule.startJob(() => {
  console.log(new Date())
})
stopJob()

Job#start(): void

Start this job.

job.start()

Job#stop(): void

Stop this job.

job.stop()

Development

# Install dependencies
> yarn

# Run the tests
> yarn test

# Continuously compile
> yarn dev

# Continuously run the tests
> yarn dev-test

# Build for production (automatically called by npm install)
> yarn build

Contributions

Contributions are very welcomed, either on the documentation or on the code.

You may:

  • report any issue you've encountered;
  • fork and create a pull request.

License

ISC © Vates SAS