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

cronerbly

v1.0.0

Published

David Halewood - learnerbly exercise

Downloads

6

Readme

Cronerbly

Learnerbly Coding Exercise

The Spec

We have a set of tasks, each running at least daily, which are scheduled using some simple values in a text file. You might recognise this if you have written a crontab configuration in the past.

Examples of the the scheduler config:

  • 30 1 /bin/run_me_daily
  • 45 * /bin/run_me_hourly
  • * * /bin/run_me_every_minute
  • 19 /bin/run_me_sixty_times

The first field is the minute past the hour, the second field is the hour of the day and the third is the command to run. For both cases * means that it should run for all values of that field. In the above example, run_me_daily has been set to run at 1:30 am every day and run_me_hourly at 45 minutes past the hour every hour. The fields are whitespace-separated and each entry is on a separate line.

We want you to write a command-line program that takes a single argument. This argument is the simulated 'current time' in the format HH:MM. The program should accept config lines in the form above to STDIN and output the soonest time at which each of the commands will fire and whether it is today or tomorrow. In the case when the task should fire at the simulated 'current time' then that is the time you should output, not the next one.

For example given the above examples as input and the simulated 'current time' command-line argument 16:10 the output should be:

  • 1:30 tomorrow - /bin/run_me_daily
  • 16:45 today - /bin/run_me_hourly
  • 16:10 today - /bin/run_me_every_minute
  • 19:00 today - /bin/run_me_sixty_times

Connect with me