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

lynx-cron

v1.0.0

Published

the lynx-cron adds cron features for the lynx-framework. This module should be used only in single-instances production environment

Downloads

10

Readme

lynx-cron

Cron module for the Lynx framework.

This module adds a cron subsystem to your lynx application, wrapping the usual cron libraries (more specifically https://github.com/kelektiv/node-cron).

Each cron job shall be a working GET endpoint, that will be executed at a certain time, using the usual cron job specification.

A job is considered successfully completed if its status code is 200. Usual http errors code, like 400 or 500, can be used to signal an error. In this case, the job will be rescheduled, until the maximum number of retry is reached, or if its status code is 200.

Notes

This CronModule implementation can be only used in an environment where the lynx application is executed as a single instance. Otherwise, each job could be executed more then once. In such environment, a more sophisticated cron module is recommended.

Installation

npm install --save lynx-cron

Dependencies

Only the lynx-framework, of course :D

Usage

In your main app file:

import CronModule from "lynx-cron";
...

let myConfig = new ConfigBuilder(__dirname).build();

const app = new App(myConfig, [new CronModule()]);
app.startServer(port);

The CronModule can be also be easily accessed as a singleton:

let cronModule = CronModule.get();

A job can be registered using the addJob method:

cronModule.addJob('00 30 11 * * 1-5', 'http://localhost:3000/jobs/invoices?authkey=123123123');

End, in the same way, a job can be deleted using the removeJob method:

cronModule.removeJob('00 30 11 * * 1-5', 'http://localhost:3000/jobs/invoices?authkey=123123123');

By default, each registered job is saved in the db, using the CronJobEntity. In this way, a cron job can survive multiple crash or restart of the lynx app.