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

expresser-cron

v3.1.1

Published

Task scheduler plugin for Expresser.

Downloads

38

Readme

Expresser Cron

The Cron is a built-in scheduled jobs manager. You can use it by loading jobs from JSON files or by calling its methods programmatically.

Loading from json

By default settings.cron.loadOnInit == true the Cron will look for a cron.json file and load it on init. You can also load your own specific files by calling the cron.load method passing the filename and general options.

The most important options are autoStart and basePath. If autoStart is true, it will run all jobs straight away when loading. The basePath sets the base path relative to the app root where the specified module / scripts are located. So for example if you want to load scripts from files located on /lib/modules/, call load("my_cron_filename.json", {basePath: "lib/modules/"}).

A sample of a cron.json file:

{
    "mydatabase.coffee": [
        {
            "callback": "cleanup",
            "args": ["collection1", "collection2"],
            "description": "Clean database every 300 seconds.",
            "schedule": 300,
            "enabled": true
        },
        {
            "callback": "report",
            "description": "Send database reports 3 times a day. Temporarily disabled.",
            "schedule": ["11:00:00", "18:00:00", "23:00"],
            "enabled": false
        }
    ],
    "controller.coffee": [
        {
            "callback": "verifySomething",
            "args": "something here",
            "description": "Verify something every 2 minutes.",
            "schedule": 120,
            "enabled": true
        }
    ]
}

And a brief description of the properties of a cron.json file:

  • mydatabase.coffee The filename of the module / script which contains the methods to be executed by the cron. It's value must be an array with the details specified below. ** callback The name of the method to be executed. ** args Optional arguments to be passed along the callback. ** description Brief description of the cron job. ** schedule Interval in seconds if a number, or an array of specific times of the day. ** enabled If false, the job won't be scheduled, default is true.

The callback will receive the full job specification as argument. So you can add extra properties to the job specification and access them inside the callback. For example:

function cleanup(job) {
  console.log(job.description);
  doCleanUp(job.args);
}

Adding jobs programmatically

Use the cron.add(jobId, jobSpecs) method, passing an optional job ID and the following specifications:

  • callback The function to be executed.
  • schedule Interval in seconds if a number, or an array of specific times of the day.
  • description Optional, job description.
  • once Optional, if true it will run the job only once.

Please note that if settings.cron.allowReplacing is false, adding an existing job (same ID) won't be allowed.

Controlling jobs programmatically

To stop jobs (won't run on schedule anymore), use the cron.stop method passing the job ID or a filter. Filters can be any job property, like its module name or description.

To start jobs again (in case they were stopped before), use the cron.start method. Same thing as stopping, pass the ID or filter.


For detailed info on specific features, check the annotated source on /docs folder.