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 🙏

© 2025 – Pkg Stats / Ryan Hefner

cron-router

v1.0.0

Published

A simple express middleware to route traffic based on server time.

Readme

cron-router

About

Cron-router is a simple middleware for express which enables routing based on server time. This was initially written to enable a small parasitic art festival to occur on the www.safari.org.au website during the 2016 SafARI festival. The alternative programming hijacked the official website between 9pm to 9am AEST and was different based on the day of the week.

Usage:

cron-router exposes one function cronRoute which takes one argument, and array of Match objects.

Match object should look like this:

var match = {
	match: {
		year: /* optional, number or {from: number, to: number } */
		month: /* optional, number or {from: number, to: number } */
		date: /* optional, number or {from: number, to: number } */
		day: /* optional number or {from: number, to: number } */
		hours: /* optional number or {from: number, to: number } */
		minutes: /* optional number or {from: number, to: number } */
	},
	route: /* an express Router */
}

Match properties (year, month, date, etc) accept either an explicit number or a range object {from: x, to: y}. CronRouter compares all the provided match values to the current server date and if equal or within the inclusive range, the request is passed to the provided express router.

example:

var express	= require('express');
var cronrouter = require('cron-router');

var app = express();

var route_A = express.Router();
route_A.get('/',(req,res)=>{
	res.send('route A is active between 9pm to midnight on Sundays.');
});)
var route_B = express.Router();
route_B.get('/',(req,res)=>{
	res.send('route B is active between midnight to 9am on Mondays.');
});)

var matches = [
	{
		match: {
			day: 0,
			hours: {from: 9, to: 24}
		},
		route: route_A
	},{
		match: {
			day: 1, //sub
			hours: {from: 0, to: 8}
		},
		route: route_B
	},
];

app.use(cronrouter.cronRoute(matches));

//if no matches it 
app.get('/', (req,res)=> {
	res.send('This is the default if none of the cron-routes are matched.');
});

app.listen(8080, (err, suc)=> {
	if (err) {
		throw err;
	} else {
		console.log('listening');
	}
});